Triple
T9793918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 216 (unused number) |
E237670
|
entity |
| Predicate | isBusinessRoute |
P90002
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Interstate 216 (unused number), isBusinessRoute, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusinessRoute Context triple: [Interstate 216 (unused number), isBusinessRoute, false]
-
A.
hasBusinessRoute
Indicates that there exists an established commercial or service route connecting two business-related entities.
-
B.
isInBusinessDistrict
Indicates that an entity is located within a designated business or commercial district area.
-
C.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
D.
isStrategicRouteFor
Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
-
E.
hasBusinessTypeAlong
Indicates that a business or commercial entity located along a route, corridor, or area is associated with a specific type or category of business activity.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda347b6bc8190a99b7dec1650cd46 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:28 p.m.