Triple
T32437185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TB-11 |
E828905
|
entity |
| Predicate | operatedInConflictEra |
P32860
|
FINISHED |
| Object | pre–World War I 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: pre–World War I period | Statement: [TB-11, operatedInConflictEra, pre–World War I period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInConflictEra Context triple: [TB-11, operatedInConflictEra, pre–World War I period]
-
A.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
-
B.
builtDuringConflict
Indicates that the construction of one entity occurred while a specified conflict or war was taking place.
-
C.
conflictEra
chosen
Indicates that two entities are associated with the same historical period or era of conflict.
-
D.
developedDuringConflict
Indicates that something was created, advanced, or significantly progressed while an identified conflict (such as a war, dispute, or crisis) was ongoing.
-
E.
hasHistoricalPeriodOfConflict
Indicates that there exists a specific historical period during which the related entities were engaged in conflict or hostilities.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.