Triple
T25675037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yusuf Pathan |
E643780
|
entity |
| Predicate | careerFormat |
P158975
|
FINISHED |
| Object | One Day International cricket |
—
|
NE NERFINISHED |
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: One Day International cricket | Statement: [Yusuf Pathan, careerFormat, One Day International cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careerFormat Context triple: [Yusuf Pathan, careerFormat, One Day International cricket]
-
A.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
C.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
D.
seasonFormatIncludes
Indicates that a particular season uses or contains a specified format as part of its structure or presentation.
-
E.
trialFormat
Indicates the specific structure, rules, or procedural setup under which a trial or experimental process is conducted.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3648848190bd3229ed424d5545 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7:36 p.m.