Triple
T31749002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iriya Gate |
E810355
|
entity |
| Predicate | hasTicketMachinesNearby |
P61741
|
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: [Iriya Gate, hasTicketMachinesNearby, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketMachinesNearby Context triple: [Iriya Gate, hasTicketMachinesNearby, yes]
-
A.
hasTicketBooths
Indicates that one entity possesses or contains ticket booths used for selling or distributing tickets.
-
B.
ticketMachines
chosen
Indicates that there is a relationship involving ticket machines, typically denoting where they are located, available, or associated with a particular entity or place.
-
C.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
D.
hasSelfServiceTicketMachines
Indicates that an entity is equipped with self-service ticket machines available for use.
-
E.
hasOutletNear
Indicates that one entity has a physical outlet or branch located in close proximity to another specified location or entity.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 30, 2026, 11:27 p.m.