Triple
T18912944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumar Sangakkara |
E462650
|
entity |
| Predicate | testTripleCenturies |
P64585
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Kumar Sangakkara, testTripleCenturies, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testTripleCenturies Context triple: [Kumar Sangakkara, testTripleCenturies, 1]
-
A.
madeTripleCenturyInTests
chosen
Indicates that a player has scored 300 or more runs in a single Test cricket innings.
-
B.
isBattingTripleCrown
Indicates that a player is simultaneously leading a league in batting average, home runs, and runs batted in.
-
C.
testDoubleCenturies
Indicates that an entity (typically a player) has achieved two or more scores of 200 or more runs in individual innings, usually within a specified context such as a series, career, or match format.
-
D.
tripleCrownSequence
Indicates that the entities participate in or represent the ordered sequence of events, titles, or achievements that together constitute a "triple crown."
-
E.
tripleCrownLeg
Indicates that the subject is a specific leg or stage within a Triple Crown series of events or competitions.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c624516c81909e6bf04707d3c71c |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.