Triple
T3119062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INDOPACOM |
E65134
|
entity |
| Predicate | establishedAsPredecessorCommand |
P45469
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [INDOPACOM, establishedAsPredecessorCommand, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsPredecessorCommand Context triple: [INDOPACOM, establishedAsPredecessorCommand, 1947]
-
A.
openedAsPredecessor
Indicates that one entity was opened or began operation as the predecessor to another entity, which later replaced or succeeded it.
-
B.
predecessorControl
Indicates that one entity has control or authority over another entity that precedes it in a sequence, process, or hierarchy.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
successorInCommand
Indicates that one entity is designated to assume command authority immediately after another entity, typically when the latter is unavailable or their term ends.
-
E.
programPredecessor
Indicates that one program temporally or logically precedes another in a sequence or hierarchy of programs.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e975f08190a91a01f37a31b766 |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.