Triple
T25995782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prague public transport network |
E646480
|
entity |
| Predicate | usesTicketValidation |
P70929
|
FINISHED |
| Object | metro station validators |
—
|
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: metro station validators | Statement: [Prague public transport network, usesTicketValidation, metro station validators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketValidation Context triple: [Prague public transport network, usesTicketValidation, metro station validators]
-
A.
usesTicketValidatorType
chosen
Indicates that an entity employs or is associated with a specific type or category of ticket validation device or method.
-
B.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
C.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
D.
hasTicketAccess
Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
-
E.
usedInE-tickets
Indicates that something (such as a method, technology, or feature) is employed or applied within the context of electronic tickets (e-tickets).
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6054b64208190bd39ea3838c9e25c |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 8:57 a.m.