Triple
T27975715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PGPL |
E706483
|
entity |
| Predicate | includesCompetitionFormat |
P2673
|
FINISHED |
| Object | round-robin |
—
|
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: round-robin | Statement: [PGPL, includesCompetitionFormat, round-robin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCompetitionFormat Context triple: [PGPL, includesCompetitionFormat, round-robin]
-
A.
appliesToCompetitionFormat
Indicates that something is relevant or specifically designed for a particular competition format.
-
B.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
C.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
D.
competitionFoundedFormat
Indicates the type or structure of the format in which a competition was originally founded.
-
E.
affectedCompetitionFormat
Indicates that one entity caused a change or influence on the structure, rules, or format of a competition.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 27, 2026, 7:41 p.m.