Triple
T13658626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion of the United States |
E326923
|
entity |
| Predicate | typeOfUnitStructure |
P111029
|
FINISHED |
| Object | combined-arms formation |
—
|
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: combined-arms formation | Statement: [Legion of the United States, typeOfUnitStructure, combined-arms formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfUnitStructure Context triple: [Legion of the United States, typeOfUnitStructure, combined-arms formation]
-
A.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
B.
hasUnitStructure
Indicates that an entity possesses a specific internal organization or arrangement that defines its structural composition.
-
C.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
D.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
-
E.
spatialUnitType
Indicates the specific kind or category of spatial unit (e.g., parcel, building, region) that characterizes the spatial entity in question.
- F. None of above. chosen
Provenance (4 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61f0d808190b1cd2a6ba0d930eb |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:52 p.m.