Triple
T18570725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aravinda de Silva |
E453865
|
entity |
| Predicate | odiCapNumberForSriLanka |
P23197
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [Aravinda de Silva, odiCapNumberForSriLanka, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: odiCapNumberForSriLanka Context triple: [Aravinda de Silva, odiCapNumberForSriLanka, 40]
-
A.
odiCapNumber
chosen
Indicates the unique sequential cap number assigned to a player for their debut in One Day International (ODI) cricket.
-
B.
t20iCapNumber
Indicates that an entity has a specific cap number (e.g., a player’s official cap or appearance number) assigned to it.
-
C.
testCapNumberForWestIndies
Indicates the assigned cap number used to identify a player who has represented the West Indies cricket team.
-
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.
operatorCapacity
Indicates the maximum workload or volume of tasks that an operator is able to handle within a given context or time frame.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b01331c8190bec3aba40358a843 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.