Triple
T21975399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Mixed Doubles Curling Championship |
E542691
|
entity |
| Predicate | numberOfPlayersPerTeamOnIce |
P3766
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [World Mixed Doubles Curling Championship, numberOfPlayersPerTeamOnIce, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPlayersPerTeamOnIce Context triple: [World Mixed Doubles Curling Championship, numberOfPlayersPerTeamOnIce, 2]
-
A.
numberOfPlayersOnIcePerTeam
chosen
Indicates the count of players from a single team who are on the ice at the same time during play.
-
B.
numberOfPlayersPerTeam
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
-
C.
hasNumberOfGoaltenders
Indicates the specific count of goaltenders associated with a given team, roster, or game context.
-
D.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
E.
originalPlayersPerTeam
Indicates the number of players that each team initially had at the start of a game or season.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f124886418819091daed0988432350 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:03 p.m.