Triple
T19816903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dome-mae Station |
E476080
|
entity |
| Predicate | servesVisitors |
P22278
|
FINISHED |
| Object | Kyocera Dome Osaka spectators |
—
|
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: Kyocera Dome Osaka spectators | Statement: [Dome-mae Station, servesVisitors, Kyocera Dome Osaka spectators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesVisitors Context triple: [Dome-mae Station, servesVisitors, Kyocera Dome Osaka spectators]
-
A.
visitorService
Indicates a relationship where a service is provided specifically for or to visitors, such as assistance, information, or support during their visit.
-
B.
hasVisitorServices
chosen
Indicates that an entity provides services or facilities specifically intended for visitors or guests.
-
C.
primaryVisitors
Indicates that certain entities are the main or most important visitors associated with another entity or context.
-
D.
receivesVisitorsEspeciallyIn
Indicates that an entity regularly accepts or hosts visitors particularly in a specified place, context, or time period.
-
E.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654f9c5b08190987237f5144c3b37 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.