Triple
T34539569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pool C (2019 Rugby World Cup) |
E886767
|
entity |
| Predicate | bonusPointForTries |
P62973
|
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), bonusPointForTries, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bonusPointForTries Context triple: [Pool C (2019 Rugby World Cup), bonusPointForTries, 1]
-
A.
pointsAwarded
Indicates that a specified number of points has been granted to an entity as a result of some action or event.
-
B.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
C.
pointsEarnedFrom
chosen
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
-
D.
penaltyPoints
Indicates that a certain number of negative points or demerits are assigned to an entity as a consequence of a rule violation, error, or infraction.
-
E.
bonusCategory
Indicates the classification or type of bonus associated with an entity or transaction.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71ff1a86481908210dffd1bd27001 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.