Triple
T19342400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States frontier army |
E483788
|
entity |
| Predicate | typicalBranchComposition |
P22486
|
FINISHED |
| Object | cavalry units |
—
|
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: cavalry units | Statement: [United States frontier army, typicalBranchComposition, cavalry units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBranchComposition Context triple: [United States frontier army, typicalBranchComposition, cavalry units]
-
A.
branchComposition
Indicates that one branch or subdivision is structurally or functionally composed of, or made up from, another entity or set of entities.
-
B.
isPartOfBranchTypically
chosen
Indicates that something is typically a component or subdivision within a larger branch.
-
C.
serviceBranchComposition
Indicates the relationship between a military service branch and the types or proportions of personnel or units that make up its overall composition.
-
D.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
E.
uniformBranch
Indicates that multiple entities share the same branch, division, or organizational unit within a larger structure.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185795bc8190a63061ca794c0d67 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.