Triple
T5495228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Call-A-Ride |
E144194
|
entity |
| Predicate | serviceRelation |
P12758
|
FINISHED |
| Object | complements MetroBus |
—
|
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: complements MetroBus | Statement: [Metro Call-A-Ride, serviceRelation, complements MetroBus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceRelation Context triple: [Metro Call-A-Ride, serviceRelation, complements MetroBus]
-
A.
relatedService
chosen
Indicates that one service is connected or associated with another service in a relevant or dependent way.
-
B.
stepRelation
Indicates a relationship where one entity is a step-relative of another, such as a stepparent, stepchild, or stepsibling connection.
-
C.
reportsRelationship
Indicates that one entity formally provides information, findings, or status about another entity or situation.
-
D.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
-
E.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
- F. None of above.
Provenance (3 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:31 p.m.