Triple
T24383879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Felton, Delaware |
E614686
|
entity |
| Predicate | primaryHighwayAccess |
P12245
|
FINISHED |
| Object | U.S. Route 13 |
—
|
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: U.S. Route 13 | Statement: [Town of Felton, Delaware, primaryHighwayAccess, U.S. Route 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHighwayAccess Context triple: [Town of Felton, Delaware, primaryHighwayAccess, U.S. Route 13]
-
A.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
B.
connectsToHighway
chosen
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
C.
isOnlyMajorRoadAccessTo
Indicates that one road is the sole major roadway providing access to a particular place or area.
-
D.
hasSeparateAccessRoad
Indicates that an entity is served by its own distinct access road, separate from other routes or shared entrances.
-
E.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294533b3881908c228a021c254006 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.