Triple
T1589867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrier Strike Group |
E34153
|
entity |
| Predicate | doctrineOrigin |
P11295
|
FINISHED |
| Object | Cold War era |
—
|
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: Cold War era | Statement: [Carrier Strike Group, doctrineOrigin, Cold War era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineOrigin Context triple: [Carrier Strike Group, doctrineOrigin, Cold War era]
-
A.
doctrineSourceFor
chosen
Indicates that one entity serves as the originating basis or authoritative source of doctrine, teachings, or principles for another entity.
-
B.
doctrineExplainedBy
Indicates that an explanation or interpretation is provided for a particular doctrine by a specified source or agent.
-
C.
stateDoctrine
Indicates that a state or government officially endorses, promotes, or is guided by a particular doctrine, ideology, or set of principles.
-
D.
doctrineName
Indicates that one entity is the formal or recognized name of a particular doctrine associated with another entity.
-
E.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.