Triple
T21631600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Junior Curling Championships |
E533842
|
entity |
| Predicate | hasMenTournament |
P145315
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [World Junior Curling Championships, hasMenTournament, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMenTournament Context triple: [World Junior Curling Championships, hasMenTournament, true]
-
A.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
B.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
-
C.
hasMenTeam
Indicates that an entity possesses, is associated with, or fields a men’s team.
-
D.
hasTournamentRecord
Indicates that an entity possesses a documented performance or results record in a specific tournament or set of tournaments.
-
E.
hasFightTournament
Indicates that an entity organizes, hosts, or is associated with a fight-based competition or tournament involving multiple participants.
- F. None of above. chosen
Provenance (4 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5217952c8190910c2103fb4a27d9 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:34 p.m.