Triple
T6807894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Fourteenth Army |
E156353
|
entity |
| Predicate | militaryBranchOfService |
P253
|
FINISHED |
| Object | German Army in World War II |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: German Army in World War II | Statement: [German Fourteenth Army, militaryBranchOfService, German Army in World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryBranchOfService Context triple: [German Fourteenth Army, militaryBranchOfService, German Army in World War II]
-
A.
hasMilitaryBranch
chosen
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
B.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
-
C.
militaryBranchOfGovernment
Indicates that a military organization functions as an official branch or component of a government.
-
D.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
E.
militaryBranchComponentOf
Indicates that one military branch or unit is an organizational component or subordinate part of a larger military branch or force.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30b56c48190a5b244ea7e0c669a |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.