Triple
T21411335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byron, Wisconsin |
E528176
|
entity |
| Predicate | hasRoadTransportation |
P93805
|
FINISHED |
| Object | local roads |
—
|
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: local roads | Statement: [Byron, Wisconsin, hasRoadTransportation, local roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadTransportation Context triple: [Byron, Wisconsin, hasRoadTransportation, local roads]
-
A.
hasTransportationSystem
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
-
B.
hasRoads
chosen
Indicates that there exist constructed road connections linking the related entities.
-
C.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
D.
hasGroundTransportation
Indicates that an entity provides, includes, or is connected to transportation services or options that operate on land (e.g., cars, buses, trains).
-
E.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1fe2cd08190bfaf28daae4f5233 |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:43 p.m.