Triple
T27526257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansoor Ali Khan Pataudi |
E694846
|
entity |
| Predicate | testCaptaincyTeam |
P14876
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [Mansoor Ali Khan Pataudi, testCaptaincyTeam, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testCaptaincyTeam Context triple: [Mansoor Ali Khan Pataudi, testCaptaincyTeam, India]
-
A.
teamCaptain
chosen
Indicates that one entity serves as the captain or designated leader of a particular team.
-
B.
stateTeam
Indicates that a team is officially associated with, represents, or belongs to a particular state.
-
C.
governingBodyTeam1
Indicates that the first team serves as the governing or managing body responsible for overseeing, regulating, or directing another entity or activity.
-
D.
coreTeams
Indicates that the entities are part of the same primary or central team within an organization or project.
-
E.
zonalTeamOf
Indicates that one entity is a team that belongs to, represents, or operates within a specific geographic or administrative zone of 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f305ce48190ae2a08d4ad2ba05e |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:24 p.m.