Triple
T32208153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardmore Basin |
E822726
|
entity |
| Predicate | hasTypeLocalityNearby |
P68061
|
FINISHED |
| Object | Ardmore, Oklahoma |
—
|
NE NERFINISHED |
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: Ardmore, Oklahoma | Statement: [Ardmore Basin, hasTypeLocalityNearby, Ardmore, Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeLocalityNearby Context triple: [Ardmore Basin, hasTypeLocalityNearby, Ardmore, Oklahoma]
-
A.
hasTypeLocality
Indicates the specific geographic location where an entity (typically a species or specimen) was originally found and formally described.
-
B.
containsLocality
Indicates that one place or area geographically includes or encompasses another locality within its boundaries.
-
C.
localityOf
Indicates that one entity is the specific place, area, or locality in which another entity is situated or occurs.
-
D.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
E.
hasNeighbouringLocality
chosen
Indicates that one locality is geographically adjacent to or directly borders another locality.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 1, 2026, 12:37 a.m.