Triple
T36508764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRB World Rankings |
E899840
|
entity |
| Predicate | maximumPointsChangePerMatch |
P193971
|
FINISHED |
| Object | about 2 rating points |
—
|
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: about 2 rating points | Statement: [IRB World Rankings, maximumPointsChangePerMatch, about 2 rating points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumPointsChangePerMatch Context triple: [IRB World Rankings, maximumPointsChangePerMatch, about 2 rating points]
-
A.
maxPointsPerGame
Indicates the maximum number of points an entity can score or is allowed to score in a single game.
-
B.
averageMarginOfVictory
Indicates the typical point or score difference by which one competitor or team wins over opponents across a set of contests or games.
-
C.
typicalNumberOfMatchesPerSeries
Indicates the usual or standard count of matches that are played within a single series.
-
D.
maximumAwardChanges
Indicates the highest number of times an award’s terms, value, or conditions are allowed to be changed within a defined period or context.
-
E.
inkColorChangesPerMatch
Indicates that the ink color used changes from one match to another.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: May 3, 2026, 4:10 p.m.