Triple
T8769755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mechanized Brigade |
E208426
|
entity |
| Predicate | typicalHigherFormation |
P41314
|
FINISHED |
| Object | army corps |
—
|
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: army corps | Statement: [Mechanized Brigade, typicalHigherFormation, army corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHigherFormation Context triple: [Mechanized Brigade, typicalHigherFormation, army corps]
-
A.
higherFormationType
chosen
Indicates that one entity is classified as a broader or more inclusive formation type that encompasses or organizes the other entity.
-
B.
higherFormationRole
Indicates that an entity serves in a specific role or function within a larger, higher-level organizational formation.
-
C.
typicalFormation
Indicates the usual or characteristic way in which something is formed, structured, or comes into existence.
-
D.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
E.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5eedc7188190a67d959b9af53837 |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.