Triple
T23632441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sourav Ganguly |
E583650
|
entity |
| Predicate | runsScoredInODIs |
P140700
|
FINISHED |
| Object | over 11000 |
—
|
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: over 11000 | Statement: [Sourav Ganguly, runsScoredInODIs, over 11000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsScoredInODIs Context triple: [Sourav Ganguly, runsScoredInODIs, over 11000]
-
A.
highestOdiScore
Indicates that the subject has achieved the highest individual ODI (One Day International) cricket score among the compared entities.
-
B.
captainODI
Indicates that the subject serves as the captain of the object’s team in One Day International (ODI) cricket matches.
-
C.
IndiansRunsScored
Indicates the number of runs that the Indians team has scored in a game or specific context.
-
D.
totalRunsScored
chosen
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.
-
E.
numberOfODIsAsCaptain
Indicates the total count of One Day International (ODI) cricket matches in which the entity served as team captain.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e90a6881909f19b2446f9d54f0 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.