Triple
T5603195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby World Cup 2003 matches |
E147168
|
entity |
| Predicate | frequencyOfTournament |
P65013
|
FINISHED |
| Object | every four years |
—
|
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: every four years | Statement: [Rugby World Cup 2003 matches, frequencyOfTournament, every four years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyOfTournament Context triple: [Rugby World Cup 2003 matches, frequencyOfTournament, every four years]
-
A.
gamesFrequency
Indicates how often the related entities engage in playing games together or participate in game-related activities.
-
B.
playInTournamentIntroduced
Indicates that an entity participates as a player in a specific tournament that has been newly introduced or added.
-
C.
notableTournament
Indicates that an entity is a tournament of particular significance or prominence in relation to another entity.
-
D.
scoredInTournament
Indicates that an entity achieved a score or points during a particular tournament.
-
E.
otherTournament
Indicates a relationship where one tournament is distinct from and not the same as another tournament.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020dce10c8190bf456602eec211d4 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:39 p.m.