Triple
T1581201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Washington (BB-47) |
E33764
|
entity |
| Predicate | conflictEra |
P32860
|
FINISHED |
| Object | interwar period |
—
|
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: interwar period | Statement: [USS Washington (BB-47), conflictEra, interwar period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictEra Context triple: [USS Washington (BB-47), conflictEra, interwar period]
-
A.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
B.
religiousConflictPeriod
Indicates a period of time during which conflicts or hostilities occur that are primarily motivated or structured by religious differences or tensions.
-
C.
chronologyWithinConflict
Indicates that one event or time period occurs within the temporal span of a specified conflict or war.
-
D.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
E.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
- F. None of above. chosen
Provenance (4 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69abacf991148190b20521c063f93bfd |
completed | March 7, 2026, 4:43 a.m. |
Created at: March 4, 2026, 7:27 p.m.