Triple
T25233945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sye |
E632287
|
entity |
| Predicate | hasClimacticMatch |
P30655
|
FINISHED |
| Object | rugby final against antagonist's 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: rugby final against antagonist's team | Statement: [Sye, hasClimacticMatch, rugby final against antagonist's team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimacticMatch Context triple: [Sye, hasClimacticMatch, rugby final against antagonist's team]
-
A.
hasChampionshipMatch
Indicates that an entity is associated with a specific championship-level match, typically as an organizer, participant, or host.
-
B.
hasFinalTournament
Indicates that an entity is associated with a specific tournament that serves as its final or concluding competition.
-
C.
hasFinalMatch
chosen
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
D.
hasFinalsSeries
Indicates that there exists a specific finals series associated with or assigned to a given entity.
-
E.
hasChampionshipDetermination
Indicates that an entity specifies the rules, criteria, or process by which a championship winner is determined.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:06 p.m.