Triple
T3898136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VGN |
E90420
|
entity |
| Predicate | ticketValidity |
P47115
|
FINISHED |
| Object | across multiple transport modes |
—
|
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: across multiple transport modes | Statement: [VGN, ticketValidity, across multiple transport modes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketValidity Context triple: [VGN, ticketValidity, across multiple transport modes]
-
A.
ticketValidityCovers
chosen
Indicates that the validity period or scope of a ticket extends to and includes a specified time, location, service, or condition.
-
B.
ticket
Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
-
C.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
D.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
E.
hasValidityPeriod
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.