Triple
T34539562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pool C (2019 Rugby World Cup) |
E886767
|
entity |
| Predicate | totalMatchesScheduled |
P6413
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Pool C (2019 Rugby World Cup), totalMatchesScheduled, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalMatchesScheduled Context triple: [Pool C (2019 Rugby World Cup), totalMatchesScheduled, 10]
-
A.
numberOfGamesScheduled
chosen
Indicates the total count of games that have been planned or arranged for a given entity or time period.
-
B.
totalMatchesPlayed
Indicates the total number of matches that have been played by the referenced entity or between the related entities.
-
C.
numberOfFinalMatches
Indicates the total count of final-stage matches associated with a given entity or event.
-
D.
numberOfTestMatches
Indicates the total count of test matches associated with a given entity (such as a player, team, or series) in the relationship.
-
E.
numberOfBowlGamesScheduled
Indicates the total count of bowl games that have been planned or scheduled for a given context or time period.
- 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 2:02 a.m.