Triple
T36387969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outpost 14 Sedona |
E896248
|
entity |
| Predicate | locationHint |
—
|
GENERATED |
| Object | Sedona |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationHint Context triple: [Outpost 14 Sedona, locationHint, Sedona]
-
A.
locationFocus
Indicates that the primary or most relevant location associated with an entity, event, or relation is being specified or emphasized.
-
B.
locationFound
Indicates that a particular entity is located or discovered at a specific place or position.
-
C.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
D.
possibleLocation
chosen
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
E.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
- F. None of above.
Provenance (1 batch)
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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.