Triple
T22074852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youth Test |
E545496
|
entity |
| Predicate | tossProcedure |
P10032
|
FINISHED |
| Object | coin toss to decide who bats first |
—
|
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: coin toss to decide who bats first | Statement: [Youth Test, tossProcedure, coin toss to decide who bats first]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tossProcedure Context triple: [Youth Test, tossProcedure, coin toss to decide who bats first]
-
A.
tossDecisionInFinal
Indicates the outcome of the coin toss that determines which side chooses to bat or field first in the final match.
-
B.
coinTossParticipant
chosen
Indicates that an entity takes part in a coin toss event, either as the initiator or as one of the involved participants.
-
C.
tackles
Indicates that one entity forcefully brings another entity to the ground or physically stops their movement, typically in a competitive or confrontational context.
-
D.
throwingHand
Indicates which hand (left or right) an entity primarily uses to throw.
-
E.
rollMethod
Indicates the method or technique by which a rolling action is performed or executed between entities.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b1904881909a1769ce8be39e05 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.