Triple
T22074847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youth Test |
E545496
|
entity |
| Predicate | battingOrderRules |
P146534
|
FINISHED |
| Object | same as Test cricket |
—
|
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: same as Test cricket | Statement: [Youth Test, battingOrderRules, same as Test cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingOrderRules Context triple: [Youth Test, battingOrderRules, same as Test cricket]
-
A.
battingOrderFlexibility
Indicates the degree to which the sequence of batters in a lineup can be rearranged or adjusted without violating rules or significantly reducing effectiveness.
-
B.
battingConditions
Indicates the environmental or situational factors that affect how batting is performed or how effective it is.
-
C.
battingType
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
D.
battingPosition
Indicates the specific order or spot in which a player appears in a batting lineup or batting order.
-
E.
batsInOrderTypically
Indicates that one entity typically bats in a specific position or sequence within a batting order relative to others.
- 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_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. |
| PDg | Predicate description generation | batch_69e6fad59ef48190b62a2af636918a15 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:28 p.m.