Triple
T28091803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkansas Highway 309 |
E709972
|
entity |
| Predicate | reachesAreaOf |
P34612
|
FINISHED |
| Object | Mount Magazine summit area |
—
|
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: Mount Magazine summit area | Statement: [Arkansas Highway 309, reachesAreaOf, Mount Magazine summit area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachesAreaOf Context triple: [Arkansas Highway 309, reachesAreaOf, Mount Magazine summit area]
-
A.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
B.
underliesArea
Indicates that one entity forms the foundational basis or underlying support for a particular area or domain of activity, knowledge, or influence.
-
C.
passesThroughArea
chosen
Indicates that an entity moves or extends through the spatial region defined by another entity or area.
-
D.
tieneAlcance
Indicates that something possesses or has a certain scope, reach, or range of effect in relation to something else.
-
E.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6406afe448190ad9c61220d2573b4 |
completed | May 2, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:59 p.m.