Triple
T3583202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (CV-6) |
E75847
|
entity |
| Predicate | serviceEndEra |
P48887
|
FINISHED |
| Object | early Cold War |
—
|
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: early Cold War | Statement: [USS Enterprise (CV-6), serviceEndEra, early Cold War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEndEra Context triple: [USS Enterprise (CV-6), serviceEndEra, early Cold War]
-
A.
serviceEra
chosen
Indicates the historical period or era during which a service, role, or duty was performed.
-
B.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain in effect.
-
C.
serviceRetirement
Indicates that an entity ends or withdraws a service, marking it as no longer available or in active use.
-
D.
originalServiceEnded
Indicates that a previously existing or initial service has come to an end or has been terminated.
-
E.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc104846c81908b6fbde7061464b4 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.