Triple
T26581256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frazer |
E667083
|
entity |
| Predicate | usedToBeLocatedNear |
P133903
|
FINISHED |
| Object | site of present-day Altus, Oklahoma |
—
|
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: site of present-day Altus, Oklahoma | Statement: [Frazer, usedToBeLocatedNear, site of present-day Altus, Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToBeLocatedNear Context triple: [Frazer, usedToBeLocatedNear, site of present-day Altus, Oklahoma]
-
A.
locatedNearFormer
Indicates that one entity is situated close to another entity that previously occupied a nearby or the same location.
-
B.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
C.
historicallyLocatedNear
chosen
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
D.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
-
E.
oftenLocatedNear
Indicates that one entity is frequently found in close physical proximity to another entity.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 2:03 a.m.