Triple
T4394206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 990 |
E99443
|
entity |
| Predicate | isShortestInterstateInNewYork |
P55839
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Interstate 990, isShortestInterstateInNewYork, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShortestInterstateInNewYork Context triple: [Interstate 990, isShortestInterstateInNewYork, yes]
-
A.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
B.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
C.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
-
D.
isNumberedHighway
Indicates that a roadway is officially designated and signed as a numbered highway within a road network.
-
E.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
- F. None of above. chosen
Provenance (4 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352a9c8b88190a7894a40be4996f0 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:20 p.m.