Triple
T36861806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodrich, Texas |
E910960
|
entity |
| Predicate | stateHighwayAccessVia |
P9041
|
FINISHED |
| Object | Farm to Market roads |
—
|
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: Farm to Market roads | Statement: [Goodrich, Texas, stateHighwayAccessVia, Farm to Market roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighwayAccessVia Context triple: [Goodrich, Texas, stateHighwayAccessVia, Farm to Market roads]
-
A.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
-
B.
stateHighwayConnectivity
Indicates that there is a transportation connection or linkage between locations via a designated state highway.
-
C.
roadAccessVia
chosen
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
D.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
E.
expresswayServedBy
Indicates that a particular expressway is provided with service or access by a specified facility, route, or service 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 3, 2026, 4:13 p.m.