Triple
T36387969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outpost 14 Sedona |
E896248
|
entity |
| Predicate | locationHint |
P28981
|
FINISHED |
| Object | Sedona |
E57349
|
NE 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: Sedona | Statement: [Outpost 14 Sedona, locationHint, Sedona]
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 (4 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbbc4f9081909f83c4fc506083cf |
completed | June 23, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.