Triple
T18570179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rahul Dravid |
E453853
|
entity |
| Predicate | canKeepWicket |
P132606
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rahul Dravid, canKeepWicket, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canKeepWicket Context triple: [Rahul Dravid, canKeepWicket, true]
-
A.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
B.
canMaintain
Indicates that one entity has the ability or capacity to maintain, service, or keep another entity in proper working condition.
-
C.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
D.
canOwn
Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
-
E.
canRetain
Indicates that one entity has the ability or permission to keep, hold, or maintain possession or control of another entity over time.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.