Triple
T10806624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Rugby World Cup |
E254982
|
entity |
| Predicate | poolStageFormat |
P90116
|
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: [2019 Rugby World Cup, poolStageFormat, round-robin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poolStageFormat Context triple: [2019 Rugby World Cup, poolStageFormat, round-robin]
-
A.
flatStages
Indicates that the stages or phases of an event, process, or competition are flat, meaning they lack significant variation in difficulty, elevation, or complexity across stages.
-
B.
servesStage
Indicates that an entity functions as a stage or phase within a larger process, sequence, or workflow.
-
C.
coreStageType
chosen
Indicates the specific kind or classification of a core stage within a larger process, system, or lifecycle.
-
D.
stagingStyle
Indicates how an event, performance, or scene is arranged, presented, or visually organized in a given context.
-
E.
numberOfStages
Indicates the total count of distinct stages or phases associated with a given process, event, or 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733b3f92c8190bcc85db22d77bb7d |
completed | April 9, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.