Triple
T1589591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford University Cricket Club |
E34147
|
entity |
| Predicate | leagueOrCup |
P30034
|
FINISHED |
| Object | inter-university 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: inter-university cricket | Statement: [Oxford University Cricket Club, leagueOrCup, inter-university cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueOrCup Context triple: [Oxford University Cricket Club, leagueOrCup, inter-university cricket]
-
A.
leagueCup
Indicates that an entity is a cup-style competition organized within or by a specific league.
-
B.
league2
Indicates that an entity participates in, is a member of, or is otherwise affiliated with a specific sports league or competitive organization.
-
C.
championshipLeague
Indicates that an entity is a championship-level competition or league in which teams or individuals compete for a title.
-
D.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
E.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
- F. None of above. chosen
Provenance (4 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a93aec7dc481909375726fbfb9e272 |
completed | March 5, 2026, 8:12 a.m. |
Created at: March 4, 2026, 7:27 p.m.