Triple
T25207052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Faulkner took 3 wickets for 36 runs |
E631280
|
entity |
| Predicate | bowlingEnd |
P107882
|
FINISHED |
| Object | MCG Members End |
—
|
NE NERFINISHED |
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: MCG Members End | Statement: [James Faulkner took 3 wickets for 36 runs, bowlingEnd, MCG Members End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlingEnd Context triple: [James Faulkner took 3 wickets for 36 runs, bowlingEnd, MCG Members End]
-
A.
isBowlingEndAt
chosen
Indicates that a specific location or point on a cricket field serves as a designated bowling end for delivering the ball.
-
B.
bowlingStrategy
Indicates the specific tactical approach or plan a bowler uses to deliver balls in order to challenge or dismiss a batter.
-
C.
bowlingSpecialty
Indicates that one entity has a particular area of skill or expertise in the sport of bowling with respect to another entity or context.
-
D.
bowlingCoach
Indicates that one entity serves as a coach or instructor for another entity specifically in the sport of bowling.
-
E.
bowlingMilestone
Indicates a significant achievement or landmark event related to a bowling performance or career.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474bce13c8190bcdd22cdd70490b5 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:52 p.m.