Triple
T9969109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Ryan Stone |
E195756
|
entity |
| Predicate | finalSceneLocation |
P81796
|
FINISHED |
| Object | Earth surface (lake/shore) |
—
|
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: Earth surface (lake/shore) | Statement: [Dr. Ryan Stone, finalSceneLocation, Earth surface (lake/shore)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSceneLocation Context triple: [Dr. Ryan Stone, finalSceneLocation, Earth surface (lake/shore)]
-
A.
climaxLocation
chosen
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
B.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
C.
finalSceneAction
Indicates the action or event that occurs in the concluding or final scene of a narrative or sequence.
-
D.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
E.
finalConcertLocation
Indicates the location where a concert or performance ultimately takes place, especially after any changes or planning stages.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b683ac8190ac97bd775a860d29 |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:47 p.m.