Triple
T1006663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Numbered Bicycle Route System |
E21728
|
entity |
| Predicate | firstRoutesApproved |
P1686
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [United States Numbered Bicycle Route System, firstRoutesApproved, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRoutesApproved Context triple: [United States Numbered Bicycle Route System, firstRoutesApproved, 1982]
-
A.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
B.
firstStandardApproved
chosen
Indicates that an entity is the earliest or initial standard that has received formal approval.
-
C.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
-
D.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
E.
initialReception
Indicates the nature or quality of the first response or reaction something receives when it is introduced or presented.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b51434f081909b301ad1c151af03 |
completed | March 1, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b2e7108190b338b6c19d4aff55 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.