Triple
T20315829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megatrain |
E510376
|
entity |
| Predicate | ticketScope |
P86328
|
FINISHED |
| Object | selected train services |
—
|
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: selected train services | Statement: [Megatrain, ticketScope, selected train services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketScope Context triple: [Megatrain, ticketScope, selected train services]
-
A.
ticketingScope
chosen
Indicates the range or domain within which ticketing actions (such as creation, assignment, or management of tickets) are valid or applicable.
-
B.
reservationScope
Indicates the extent or range within which a reservation applies or is valid.
-
C.
issuerScope
Indicates the range or domain of authority, responsibility, or applicability associated with the entity acting as the issuer in a given context.
-
D.
participantScope
Indicates the extent, range, or set of participants that are involved in or affected by a given relationship or action.
-
E.
typicalScope
Indicates the usual or expected range, extent, or domain within which something normally applies, operates, or is relevant.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67787af188190bc32a3049c9c5b39 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.