Triple
T29539075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminus (after leaving Trantor) |
E749437
|
entity |
| Predicate | distanceFromTrantor |
P202567
|
FINISHED |
| Object | on the periphery of the Galaxy |
—
|
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: on the periphery of the Galaxy | Statement: [Terminus (after leaving Trantor), distanceFromTrantor, on the periphery of the Galaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTrantor Context triple: [Terminus (after leaving Trantor), distanceFromTrantor, on the periphery of the Galaxy]
-
A.
distanceFromYserTower
Indicates the measured spatial distance between a given entity and the Yser Tower.
-
B.
distanceFromStar
Indicates the measured or specified spatial separation between an object and a particular star.
-
C.
distanceToPula
Indicates the measured or calculated spatial distance between a given entity and the location Pula.
-
D.
distanceFromBabylon
Indicates the spatial distance between a given location or object and the city of Babylon.
-
E.
notableLocationOnHomeworld
Indicates that a specific location is notable or significant on the entity’s homeworld.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a009273634c8190b5b9c87053b56760 |
completed | May 10, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0092171230819096e4274dd97e0410 |
completed | May 10, 2026, 2:11 p.m. |
| PDg | Predicate description generation | batch_6a009272afc88190a041b7e16d851599 |
completed | May 10, 2026, 2:13 p.m. |
Created at: April 28, 2026, 5 p.m.