Triple
T3370781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pleistoanax |
E70948
|
entity |
| Predicate | reignInterrupted |
P47652
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pleistoanax, reignInterrupted, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignInterrupted Context triple: [Pleistoanax, reignInterrupted, true]
-
A.
gameInterrupted
Indicates that an ongoing game has been stopped or disrupted before reaching its normal conclusion.
-
B.
interruptionDuration
Indicates the length of time for which an ongoing activity, process, or state is temporarily halted or disrupted.
-
C.
disruptsContinuityOf
Indicates that one entity interrupts, breaks, or otherwise prevents the ongoing, uninterrupted progression or sequence of another entity or process.
-
D.
hasHistoricalInterruptions
Indicates that the continuity of an event, process, or relationship has been broken by one or more distinct interruptions over time.
-
E.
constructionInterruptedBy
Indicates that an ongoing construction process is halted, delayed, or disrupted due to the actions or occurrence of another specified entity or event.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2bb32f88190bacf50e11b50fe99 |
completed | March 8, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada698eeb48190a1f5762fdd3b7b63 |
completed | March 8, 2026, 4:40 p.m. |
Created at: March 8, 2026, 3:13 p.m.