Triple
T22915351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casio World Open |
E568720
|
entity |
| Predicate | tourOrganizer |
P55754
|
FINISHED |
| Object | Japan Golf Tour Organization |
—
|
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: Japan Golf Tour Organization | Statement: [Casio World Open, tourOrganizer, Japan Golf Tour Organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourOrganizer Context triple: [Casio World Open, tourOrganizer, Japan Golf Tour Organization]
-
A.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
B.
tourComponentOf
Indicates that something functions as a constituent part or segment of a larger tour.
-
C.
tourPromoter
chosen
Indicates a relationship where an entity organizes, markets, or manages a tour or series of live events for another entity.
-
D.
tourismEvent
Indicates an event or activity that is organized for or significantly involves tourism, attracting visitors for leisure, cultural, or recreational purposes.
-
E.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18079217481908db98882929ac69a |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.