Triple
T27544129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Japan High School Soccer Tournament |
E695313
|
entity |
| Predicate | finalStageHeldIn |
P147837
|
FINISHED |
| Object | Kantō region |
—
|
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: Kantō region | Statement: [All Japan High School Soccer Tournament, finalStageHeldIn, Kantō region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalStageHeldIn Context triple: [All Japan High School Soccer Tournament, finalStageHeldIn, Kantō region]
-
A.
finalHeld
Indicates that an entity ultimately retains possession or control of another entity at the conclusion of a process or event.
-
B.
finalTournamentStage
Indicates that an event or match represents the concluding or championship stage of a tournament.
-
C.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
D.
statusInFinale
Indicates the role, condition, or outcome an entity has specifically in the final episode or concluding segment of a series or event.
-
E.
finalUsuallyHeldIn
chosen
Indicates that the final stage or concluding event of something is typically conducted or takes place in a particular location or venue.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 1:32 p.m.