Triple
T22356273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravi Shastri |
E552659
|
entity |
| Predicate | odiCapNumberForIndia |
P23197
|
FINISHED |
| Object | 54 |
—
|
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: 54 | Statement: [Ravi Shastri, odiCapNumberForIndia, 54]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: odiCapNumberForIndia Context triple: [Ravi Shastri, odiCapNumberForIndia, 54]
-
A.
odiCapNumber
chosen
Indicates the unique sequential cap number assigned to a player for their debut in One Day International (ODI) cricket.
-
B.
mobileNumbersHaveNoGeographicAreaCode
Indicates that mobile phone numbers are not associated with or constrained by any specific geographic area code.
-
C.
testCapNumberForSriLanka
Indicates performing a validation check on whether a given number conforms to the specific CAP numbering rules used in Sri Lanka.
-
D.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
-
E.
t20iCapNumber
Indicates that an entity has a specific cap number (e.g., a player’s official cap or appearance number) assigned to it.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157cf94508190b0f2c63ddfecb813 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.