Triple
T11048212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silmarils |
E261181
|
entity |
| Predicate | finalLocationOfOne |
P34068
|
FINISHED |
| Object | sky as a star borne by Eärendil |
—
|
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: sky as a star borne by Eärendil | Statement: [Silmarils, finalLocationOfOne, sky as a star borne by Eärendil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalLocationOfOne Context triple: [Silmarils, finalLocationOfOne, sky as a star borne by Eärendil]
-
A.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
B.
finalHomeOf
chosen
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
C.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
D.
finalCity
Indicates that a given city is the last or ultimate city associated with an entity within a sequence, process, or journey.
-
E.
firstLocation
Indicates the initial or primary place where an entity is situated, originates, or where an event or relationship begins.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798315b988190bc565581b2664009 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.