Triple
T10703231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pax Britannica |
E252332
|
entity |
| Predicate | hasEndingEvent |
P1398
|
FINISHED |
| Object | outbreak of World War I |
—
|
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: outbreak of World War I | Statement: [Pax Britannica, hasEndingEvent, outbreak of World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndingEvent Context triple: [Pax Britannica, hasEndingEvent, outbreak of World War I]
-
A.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
B.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
C.
endEvent
chosen
Indicates that one event or process marks the termination or conclusion of another event or process.
-
D.
hasConditionalEnding
Indicates that one entity concludes or terminates only if a specified condition involving another entity is met.
-
E.
hasUnfinishedEnding
Indicates that an entity concludes in an incomplete, unresolved, or open-ended manner rather than reaching a fully finished state.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fddd28d481908abc5c1d4e5a9f3e |
completed | April 9, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8ea6408190a800f9cb57372189 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.