Triple
T20157925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 7 |
E491623
|
entity |
| Predicate | hasFixedRoute |
P138884
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Line 7, hasFixedRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFixedRoute Context triple: [Line 7, hasFixedRoute, true]
-
A.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasRouteAlignment
Indicates that there is a defined spatial or geometric alignment associated with a route or pathway.
-
C.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
D.
hasMultipleRoutes
Indicates that there is more than one distinct route or path available between the related entities.
-
E.
hasBusinessRoutes
Indicates that there exist established commercial or trade routes connecting the related entities for conducting business activities.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e18a0c8190a2cc2b305da28047 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:34 p.m.