Triple
T15035969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyssa |
E378476
|
entity |
| Predicate | appearsInStory |
P795
|
FINISHED |
| Object | Terminus |
E1132715
|
NE 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: Terminus | Statement: [Nyssa, appearsInStory, Terminus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Terminus Context triple: [Nyssa, appearsInStory, Terminus]
-
A.
Terminus
Terminus was the original 19th-century name for the settlement that later became the city of Atlanta, Georgia.
-
B.
Terminus
"Terminus" is a poem by Seamus Heaney, featured in his collection *The Haw Lantern*, that reflects on themes of borders, identity, and historical division.
-
C.
Terminus
Terminus is the remote frontier planet that serves as the capital of the Foundation in Isaac Asimov’s science fiction series.
-
D.
Terminus
Terminus is the Roman god who presides over boundaries and boundary markers, symbolizing the protection and sanctity of property lines.
-
E.
Terminus
chosen
Terminus is a 1983 Doctor Who serial from the classic series, featuring the Fifth Doctor and marking the departure of the companion Nyssa.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82b29948190acda49cbec3f927a |
completed | April 15, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea5b75c04819085996a7f88ab6c38 |
completed | May 9, 2026, 3:10 a.m. |
Created at: April 10, 2026, 2:59 a.m.