Triple
T446893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Transit |
E7040
|
entity |
| Predicate | hasRouteType |
P13326
|
FINISHED |
| Object | fixed-route bus |
—
|
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: fixed-route bus | Statement: [Arlington Transit, hasRouteType, fixed-route bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteType Context triple: [Arlington Transit, hasRouteType, fixed-route bus]
-
A.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
parentRouteType
Indicates that one route type serves as the parent or higher-level category for another route type within a route hierarchy.
-
C.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
D.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
E.
hasRecordType
Indicates that an entity is associated with or classified under a specific type or category of record.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef62c7a88190851fcd57658b4102 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.