Triple
T2940005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Metro bus lines |
E79361
|
entity |
| Predicate | typicalVehicle |
P1776
|
FINISHED |
| Object | 40-foot transit 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: 40-foot transit bus | Statement: [Los Angeles Metro bus lines, typicalVehicle, 40-foot transit bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVehicle Context triple: [Los Angeles Metro bus lines, typicalVehicle, 40-foot transit bus]
-
A.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
-
B.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
D.
intendedVehicle
Indicates that one entity is the vehicle that another entity plans or is meant to use.
-
E.
vehicleTypeFocus
Indicates that the relationship or action specifically concerns or emphasizes a particular type or category of vehicle.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad986d9a248190927efc1a0c7d247f |
completed | March 8, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.