Triple
T1941958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro L Line (Los Angeles) |
E41573
|
entity |
| Predicate | isPublicTransport |
P34193
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Metro L Line (Los Angeles), isPublicTransport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicTransport Context triple: [Metro L Line (Los Angeles), isPublicTransport, yes]
-
A.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
B.
hasFormOfPublicTransit
Indicates that one entity provides or is associated with a particular type or mode of public transportation for another entity or context.
-
C.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
-
D.
hasPublicTransitMode
Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
-
E.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:36 p.m.