Triple
T9594281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daring class |
E231491
|
entity |
| Predicate | navalArchitectureEra |
P42687
|
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: [Daring class, navalArchitectureEra, early Cold War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalArchitectureEra Context triple: [Daring class, navalArchitectureEra, early Cold War]
-
A.
navalEra
chosen
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
-
B.
propulsionEra
Indicates the historical period or generation of propulsion technology associated with an entity (e.g., vehicle, engine, or system).
-
C.
navalAnalogue
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
D.
navalClassGeneration
Indicates that one naval class belongs to a particular generational sequence or iteration relative to another naval class.
-
E.
aircraftEra
Indicates the historical time period or era during which an aircraft was designed, produced, or primarily operated.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a134b0c81908a568e5d2ecfbb92 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.