Triple
T26259653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS New Haven (CL-76) |
E656811
|
entity |
| Predicate | navalTheaterEra |
P42687
|
FINISHED |
| Object | World War II 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: World War II era | Statement: [USS New Haven (CL-76), navalTheaterEra, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTheaterEra Context triple: [USS New Haven (CL-76), navalTheaterEra, World War II era]
-
A.
navalEra
chosen
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
-
B.
navalHistory
Indicates a relationship where an entity is associated with the study, record, or events of naval or maritime military history.
-
C.
navalCampaignParticipation
Indicates involvement of an entity in a specific naval campaign as a participant or contributor.
-
D.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
-
E.
sharesWorldWarTheater
Indicates that two military operations or events took place in the same theater of operations during a World War.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dfdd57c81908d069fc4b8124ff7 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:09 p.m.