Triple
T6285895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-1 |
E140897
|
entity |
| Predicate | isPublicTransportService |
P34193
|
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: [C-1, isPublicTransportService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicTransportService Context triple: [C-1, isPublicTransportService, true]
-
A.
isPublicTransport
chosen
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
B.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
C.
hasPublicTransitServiceLevel
Indicates the level or quality of public transit service provided to or available at a given location or entity.
-
D.
hasPublicTransitFunction
Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
-
E.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063fe59fc81908dbd968017771190 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.