Triple
T4573611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Day International |
E123091
|
entity |
| Predicate | fieldingCircleRules |
P57808
|
FINISHED |
| Object | applies |
—
|
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: applies | Statement: [One Day International, fieldingCircleRules, applies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldingCircleRules Context triple: [One Day International, fieldingCircleRules, applies]
-
A.
fieldingSpecialty
Indicates a player's particular area of expertise or primary role when performing defensive (fielding) duties in a sport.
-
B.
fielderMittFeature
Indicates that a baseball fielder’s mitt possesses or includes a particular feature or characteristic.
-
C.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
D.
fielded
Indicates that an entity deployed, presented, or put forward another entity (such as a person, team, or resource) for participation or use in a particular context or activity.
-
E.
usesDesignatedHitterRule
Indicates that a baseball league, team, or game employs the designated hitter rule, allowing a player to bat in place of the pitcher.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c89a5c81909a78bf0ac64777ad |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:10 p.m.