Triple
T26283860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umar Gul |
E661076
|
entity |
| Predicate | representedDomesticTeam |
P134920
|
FINISHED |
| Object | Peshawar cricket team |
—
|
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: Peshawar cricket team | Statement: [Umar Gul, representedDomesticTeam, Peshawar cricket team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedDomesticTeam Context triple: [Umar Gul, representedDomesticTeam, Peshawar cricket team]
-
A.
domesticTeam
Indicates that a team is playing at its home venue in a given match or competition.
-
B.
playedDomesticTeam
chosen
Indicates that an athlete has been a member of or has competed for a particular domestic (non-international) team.
-
C.
represented team
Indicates that an entity served as a member or official participant of a particular team, acting on its behalf in a competitive or organizational context.
-
D.
representedByTeam
Indicates that an entity is officially or formally represented by a specific team.
-
E.
stateTeamOf
Indicates that one entity is the official team representing a particular state associated with 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 26, 2026, 10:02 p.m.