Triple
T27768212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo DisneySea Station |
E701661
|
entity |
| Predicate | servesParkEntrance |
P101784
|
FINISHED |
| Object | Tokyo DisneySea main entrance |
—
|
NE NERFINISHED |
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: Tokyo DisneySea main entrance | Statement: [Tokyo DisneySea Station, servesParkEntrance, Tokyo DisneySea main entrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesParkEntrance Context triple: [Tokyo DisneySea Station, servesParkEntrance, Tokyo DisneySea main entrance]
-
A.
parkServed
Indicates that a particular park is provided with services or coverage by a specified entity (such as a transit line, facility, or administrative body).
-
B.
servesAttraction
Indicates that one entity functions as or provides a service that supports or enhances the experience of a particular attraction.
-
C.
parkEntranceLeadsTo
Indicates that a specific park entrance provides direct access or a pathway into a particular area or section of the park.
-
D.
parkEntranceArea
Indicates the area that serves as an entrance or access point to a park.
-
E.
parkEntranceStation
chosen
Indicates that a location functions as an entrance station or access point for a park.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 27, 2026, 4:32 p.m.