Triple
T4573614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Day International |
E123091
|
entity |
| Predicate | matchRefereePresent |
P28486
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [One Day International, matchRefereePresent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchRefereePresent Context triple: [One Day International, matchRefereePresent, yes]
-
A.
refereeNationality
Indicates the country or national affiliation associated with a referee.
-
B.
requiresRingOfficials
chosen
Indicates that the event or activity cannot proceed or be valid unless designated ring officials are present or assigned.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
leagueOfficiated
Indicates that a particular league is overseen, governed, or administered by a specified officiating body or authority.
-
E.
refereedMatch
Indicates that an entity served as the referee or official overseeing and enforcing the rules in a particular match or game.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c89a5c81909a78bf0ac64777ad |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.