Triple
T5044298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Support Command |
E113622
|
entity |
| Predicate | hasSuccessorType |
P60459
|
FINISHED |
| Object | field army |
—
|
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: field army | Statement: [Support Command, hasSuccessorType, field army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorType Context triple: [Support Command, hasSuccessorType, field army]
-
A.
hasNotableSuccessorType
Indicates that an entity has a successor whose type or category is considered notably significant or distinguished in relation to it.
-
B.
successorType
chosen
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
C.
isSuccessorTo
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
-
D.
hasMoreAggressiveSuccessor
Indicates that one entity is followed or replaced by another entity that exhibits a higher level of aggressiveness in behavior, strategy, or effect.
-
E.
hasModernSuccessor
Indicates that an entity is followed or replaced by another entity that serves as its modern equivalent or continuation.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fc04f08190aba851fa0192d0fb |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.