Triple
T26834789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Cup |
E675598
|
entity |
| Predicate | matchReferees |
P145297
|
FINISHED |
| Object | PCB-appointed referees |
—
|
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: PCB-appointed referees | Statement: [Pakistan Cup, matchReferees, PCB-appointed referees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchReferees Context triple: [Pakistan Cup, matchReferees, PCB-appointed referees]
-
A.
refereesInCompetition
Indicates that an entity serves as a referee or official within a particular competition or event.
-
B.
refereesInLeague
Indicates that a person serves as a referee within a particular sports league.
-
C.
matchOfficialsAppointedBy
chosen
Indicates that certain officials have been formally designated or assigned by a specified authority or organization to oversee or manage a particular match.
-
D.
matchOfficials
Indicates that certain officials are assigned to oversee, manage, or adjudicate a particular match or game.
-
E.
overseesReferees
Indicates that one entity has responsibility for supervising, managing, or directing the work and performance of referees.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61adfa2c48190b9ac02679c1d0e5d |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:04 a.m.