Triple
T23364779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men in Blue |
E593283
|
entity |
| Predicate | notableAllRounder |
P146402
|
FINISHED |
| Object | Kapil Dev |
—
|
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: Kapil Dev | Statement: [Men in Blue, notableAllRounder, Kapil Dev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAllRounder Context triple: [Men in Blue, notableAllRounder, Kapil Dev]
-
A.
isAllRounder
chosen
Indicates that an entity is proficient in multiple roles or skills, rather than being specialized in just one.
-
B.
notableBatter
Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
-
C.
notableCatcher
Indicates that the person is recognized as a prominent or distinguished catcher, typically in a sporting or professional context.
-
D.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
E.
notableShortstop
Indicates that the subject is recognized as a distinguished or prominent shortstop in baseball.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ab7fc481908b496ec9b543eddd |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.