Triple
T12315564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King in Exile |
E293589
|
entity |
| Predicate | ceasesAfterEvent |
P1398
|
FINISHED |
| Object | restoration of the Kingdom under the Mountain |
—
|
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: restoration of the Kingdom under the Mountain | Statement: [King in Exile, ceasesAfterEvent, restoration of the Kingdom under the Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasesAfterEvent Context triple: [King in Exile, ceasesAfterEvent, restoration of the Kingdom under the Mountain]
-
A.
closedAfterEvent
Indicates that an entity becomes or is marked as closed following the occurrence of a specified event.
-
B.
endEvent
chosen
Indicates that one event or process marks the termination or conclusion of another event or process.
-
C.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
D.
diesAfter
Indicates that one entity dies at a later time than another entity.
-
E.
repealedAfterEvent
Indicates that a law or regulation was repealed as a consequence of, or following, a specific event.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.