Triple
T28841173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 493 |
E728317
|
entity |
| Predicate | isContiguousWithAnyRoute |
P171008
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Interstate 493, isContiguousWithAnyRoute, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContiguousWithAnyRoute Context triple: [Interstate 493, isContiguousWithAnyRoute, no]
-
A.
isConcurrentWithOtherRoutes
Indicates that one route occurs or operates at the same time as one or more other routes.
-
B.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
C.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
D.
hasCommonRoute
Indicates that two or more entities share at least one overlapping or identical route or path.
-
E.
isRelatedRouteOf
Indicates that one route is connected to, associated with, or serves as an alternative or complementary path to another route.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 28, 2026, 6:40 a.m.