Triple
T8309195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Intrepid |
E194545
|
entity |
| Predicate | coldWarService |
P24788
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [USS Intrepid, coldWarService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coldWarService Context triple: [USS Intrepid, coldWarService, yes]
-
A.
statusDuringColdWar
Indicates the political or diplomatic status or alignment that an entity held specifically during the Cold War period.
-
B.
statusAfterColdWar
Indicates the condition or standing of an entity in the period following the end of the Cold War.
-
C.
roleDuringColdWar
chosen
Indicates the specific position, function, or involvement an entity had in the context of the Cold War period.
-
D.
partOfColdWarContext
Indicates that something occurs within, contributes to, or is significantly shaped by the geopolitical, ideological, or military dynamics of the Cold War period.
-
E.
countryDuringWar
Indicates that a country exists or participates as a relevant actor during a specified war or armed conflict.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2d2c30819095075940479b75a7 |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.