Triple
T33840609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger Binny |
E867347
|
entity |
| Predicate | Stuart BinnyOccupation |
P177772
|
FINISHED |
| Object | Indian cricketer |
—
|
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: Indian cricketer | Statement: [Roger Binny, Stuart BinnyOccupation, Indian cricketer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Stuart BinnyOccupation Context triple: [Roger Binny, Stuart BinnyOccupation, Indian cricketer]
-
A.
postCricketOccupation
Indicates the occupation or professional role a person takes up after their cricket-playing career has ended.
-
B.
roleInIndianFootball
Indicates that an entity holds or has held a specific role, position, or function within the context of Indian football.
-
C.
notableBatsmanForIndia
Indicates that a person is recognized as a notable batsman who has played cricket for the Indian national team.
-
D.
notableBowlerForIndia
Indicates that a person is recognized as a prominent or distinguished bowler who has represented India in cricket.
-
E.
isBatsman
Indicates that an entity plays the role or performs the function of a batsman in a batting context.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:47 a.m.