Triple
T20121843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 285 (North Carolina) |
E490626
|
entity |
| Predicate | isConnectorRouteFor |
P130931
|
FINISHED |
| Object | Winston-Salem 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: Winston-Salem area | Statement: [Interstate 285 (North Carolina), isConnectorRouteFor, Winston-Salem area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectorRouteFor Context triple: [Interstate 285 (North Carolina), isConnectorRouteFor, Winston-Salem area]
-
A.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
B.
isScenicConnectorBetween
Indicates that something serves as a visually appealing route or link connecting two locations or entities.
-
C.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
D.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
E.
isRelatedRouteOf
chosen
Indicates that one route is connected to, associated with, or serves as an alternative or complementary path to another route.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6673f5b4c8190bf9fb5f4e6b6a452 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:30 p.m.