Triple
T22074594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amol Muzumdar |
E545490
|
entity |
| Predicate | teamCaptaincy |
P14876
|
FINISHED |
| Object | captain of Mumbai in domestic cricket |
—
|
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: captain of Mumbai in domestic cricket | Statement: [Amol Muzumdar, teamCaptaincy, captain of Mumbai in domestic cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamCaptaincy Context triple: [Amol Muzumdar, teamCaptaincy, captain of Mumbai in domestic cricket]
-
A.
teamCaptain
chosen
Indicates that one entity serves as the captain or designated leader of a particular team.
-
B.
homeTeamCaptain
Indicates that one entity serves as the captain of the home team in a given game or match in relation to the other entity.
-
C.
captainedRepresentativeTeam
Indicates that an entity has served as the captain of a representative (e.g., national or regional) team.
-
D.
awayTeamCaptain
Indicates that one entity serves as the captain or designated leader of the away (visiting) team in a competition or match.
-
E.
teamChampionHeadCoach
Indicates that a coach served as the head coach of a team during a season or event in which that team won a championship.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288affb081908b64742f7bf467fa |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.