Triple
T8451738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost River |
E199814
|
entity |
| Predicate | reemergenceLocation |
P63451
|
FINISHED |
| Object | near Wardensville, West Virginia |
—
|
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 Wardensville, West Virginia | Statement: [Lost River, reemergenceLocation, near Wardensville, West Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reemergenceLocation Context triple: [Lost River, reemergenceLocation, near Wardensville, West Virginia]
-
A.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
B.
reappearsAt
chosen
Indicates that an entity, after having disappeared or been absent, becomes present again at a specific location or point in time.
-
C.
immediateAftermathLocation
Indicates the location where the direct and immediate consequences of an event take place.
-
D.
notableRevivalLocation
Indicates that a place is recognized as a significant site where something (such as a work, practice, or tradition) was revived or brought back into prominence.
-
E.
exileLocation
Indicates the place or destination to which an entity is sent or kept in exile.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe449decc8190bd62f077427f9634 |
completed | March 31, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.