Triple
T18485947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Lost River |
E451688
|
entity |
| Predicate | hasDisappearanceLocation |
P19453
|
FINISHED |
| Object | near Arco, Idaho |
—
|
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: near Arco, Idaho | Statement: [Big Lost River, hasDisappearanceLocation, near Arco, Idaho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisappearanceLocation Context triple: [Big Lost River, hasDisappearanceLocation, near Arco, Idaho]
-
A.
placeOfDisappearance
chosen
Indicates the location where an entity was last seen or went missing.
-
B.
intendedDestinationAtTimeOfDisappearance
Indicates the location or place an entity was planning to go to at the specific time when it disappeared.
-
C.
timeOfDisappearance
Indicates the specific time at which an entity disappeared or was last observed to no longer be present.
-
D.
disappearedDuring
Indicates that an entity ceased to be observable or present during the time span or event associated with another entity.
-
E.
disappearanceStatus
Indicates the state or condition of whether and how something or someone has gone missing or ceased to be present.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d722808190a97828cae8e3846e |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.