Triple
T34539570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pool C (2019 Rugby World Cup) |
E886767
|
entity |
| Predicate | bonusPointForNarrowLoss |
P179664
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Pool C (2019 Rugby World Cup), bonusPointForNarrowLoss, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bonusPointForNarrowLoss Context triple: [Pool C (2019 Rugby World Cup), bonusPointForNarrowLoss, 1]
-
A.
loserPoints
Indicates the number of points awarded to or accumulated by the losing side in a competitive event or comparison.
-
B.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
C.
usesPointsForLoss
Indicates that a system or rule assigns or deducts points to represent or account for a loss.
-
D.
bonusCategory
Indicates the classification or type of bonus associated with an entity or transaction.
-
E.
loserScore
Indicates the number of points or score achieved by the losing participant in a competitive event or comparison.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:02 a.m.