Triple
T5737750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Blaster |
E126539
|
entity |
| Predicate | referredPersonRole |
P4342
|
FINISHED |
| Object | top-order batsman |
—
|
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: top-order batsman | Statement: [Master Blaster, referredPersonRole, top-order batsman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referredPersonRole Context triple: [Master Blaster, referredPersonRole, top-order batsman]
-
A.
refersToRole
chosen
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
B.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
C.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
D.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
E.
beneficiaryRole
Indicates that one entity serves as the beneficiary or recipient of an action, service, or resource provided by another entity.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255c8c308190821f968ec41c5078 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.