Triple
T3020759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naha Tug-of-War Festival |
E82447
|
entity |
| Predicate | participantsSide |
P15194
|
FINISHED |
| Object | East team |
—
|
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: East team | Statement: [Naha Tug-of-War Festival, participantsSide, East team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantsSide Context triple: [Naha Tug-of-War Festival, participantsSide, East team]
-
A.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
C.
participant
Indicates that an entity takes part in, is involved in, or plays a role within a specified event, activity, or process.
-
D.
teamParticipated
chosen
Indicates that a team took part in or was involved in a particular event, activity, or competition.
-
E.
opposingParticipants
Indicates that the related entities are participants positioned in opposition to each other within the same interaction, event, or context.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a951e688190b3e35909affd3bfd |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.