Triple
T11151542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby World Cup 2027 |
E263796
|
entity |
| Predicate | hasOpeningMatch |
P23679
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rugby World Cup 2027, hasOpeningMatch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningMatch Context triple: [Rugby World Cup 2027, hasOpeningMatch, yes]
-
A.
hasOpeningMatchSeason
Indicates that an entity has a specific match designated as the opening match of a particular season.
-
B.
openingMatch
chosen
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
C.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
D.
openingMatchResult
Indicates the outcome or result associated with the opening match in a series, tournament, or competition.
-
E.
hasOpeningMovement
Indicates that a work, performance, or sequence includes a distinct initial movement or section that begins the overall piece.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8719e74819095413abc6c79296c |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce71944819089eee9b5c9283cbd |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.