Triple
T32095505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Undying Lands |
E819712
|
entity |
| Predicate | finalDestinationOf |
P96320
|
FINISHED |
| Object | Frodo Baggins |
—
|
NE NERFINISHED |
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: Frodo Baggins | Statement: [The Undying Lands, finalDestinationOf, Frodo Baggins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDestinationOf Context triple: [The Undying Lands, finalDestinationOf, Frodo Baggins]
-
A.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
B.
destinationOnFinalVoyage
chosen
Indicates the place where an entity ultimately arrived or was intended to arrive on its final journey or last voyage.
-
C.
finalRoute
Indicates that a given route represents the completed, chosen, or ultimate path or sequence among possible alternatives.
-
D.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
E.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 12:25 a.m.