Triple
T12763313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | みどりの窓口 |
E305049
|
entity |
| Predicate | ticketTypeSold |
P106772
|
FINISHED |
| Object | 乗車券 |
—
|
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: 乗車券 | Statement: [みどりの窓口, ticketTypeSold, 乗車券]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketTypeSold Context triple: [みどりの窓口, ticketTypeSold, 乗車券]
-
A.
ticketsSold
Indicates that a certain number of tickets have been purchased or distributed for a particular event or offering.
-
B.
ticketTypeStored
Indicates that a particular type of ticket has been recorded and saved in a storage or system.
-
C.
ticketTypeExample
Indicates that an entity serves as an example or illustrative instance of a particular ticket type.
-
D.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
E.
ticketingProduct
Indicates a relationship where an entity is associated with, or offered as, a ticketing-related product (such as a service or item used for issuing, managing, or selling tickets).
- F. None of above. chosen
Provenance (4 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8f9f588190bffdea878856204b |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:28 p.m.