Triple
T24072134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minimetrò |
E596261
|
entity |
| Predicate | isUrbanTransitMode |
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: [Minimetrò, isUrbanTransitMode, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanTransitMode Context triple: [Minimetrò, isUrbanTransitMode, yes]
-
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.
hasFormOfPublicTransit
Indicates that one entity provides or is associated with a particular type or mode of public transportation for another entity or context.
-
C.
isPublicTransportIn
Indicates that a mode or instance of public transportation operates within, serves, or is located in a specified area or region.
-
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.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db1aad248190a1d25c64cc5016eb |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.