Triple
T25207035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Faulkner took 3 wickets for 36 runs |
E631280
|
entity |
| Predicate | runsConceded |
P158030
|
FINISHED |
| Object | 36 |
—
|
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: 36 | Statement: [James Faulkner took 3 wickets for 36 runs, runsConceded, 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsConceded Context triple: [James Faulkner took 3 wickets for 36 runs, runsConceded, 36]
-
A.
battedRuns
Indicates that a player scored a specified number of runs while batting in a cricket (or similar bat-and-ball) context.
-
B.
battedRunsScored
Indicates the number of runs a player scores as a direct result of their own batting actions.
-
C.
perfectGameRunsAllowed
Indicates that in a perfect game, the number of runs allowed by the pitcher or team is recorded or constrained to a specific value (typically zero).
-
D.
goalsConceded
Indicates the number of goals a team or player has allowed the opposing side to score.
-
E.
totalRunsScored
Indicates the total number of runs that have been scored by a specified entity (such as a player or team) over a defined context or period.
- 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_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. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:52 p.m.