Triple
T18599042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricky Ponting |
E454570
|
entity |
| Predicate | odiMatches |
P23205
|
FINISHED |
| Object | 375 |
—
|
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: 375 | Statement: [Ricky Ponting, odiMatches, 375]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: odiMatches Context triple: [Ricky Ponting, odiMatches, 375]
-
A.
odiMatchesPlayed
chosen
Indicates the number of One Day International (ODI) cricket matches that have been played by or between the referenced entities.
-
B.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
C.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
-
D.
finalMatches
Indicates that two or more items correspond exactly in their final or completed form, satisfying all criteria for being considered the same at the end state.
-
E.
darkMatch
Indicates a relationship where two entities are matched or aligned in a hidden, non-public, or preliminary context not visible in the main or standard view.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474f1d548190b74408eabd396344 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.