Triple
T23365816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metrobus services |
E593316
|
entity |
| Predicate | routeCoverage |
P152441
|
FINISHED |
| Object | inner-city routes |
—
|
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: inner-city routes | Statement: [Metrobus services, routeCoverage, inner-city routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeCoverage Context triple: [Metrobus services, routeCoverage, inner-city routes]
-
A.
routeAvailability
Indicates whether a particular route between two points is currently available for use.
-
B.
routeTypeAccessed
Indicates that a particular type of route has been accessed or used in some context.
-
C.
routeDescription
Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
-
D.
routesFrom
Indicates that something (such as a path, connection, or communication) originates at one entity and is directed or carried from that source entity toward another.
-
E.
routingCapability
Indicates the ability of an entity to determine and direct the path that data, messages, or items should take through a network or 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ac7494819082e98ac5632eba28 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 5:31 p.m.