Triple
T31453195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic Games rugby sevens tournament |
E802378
|
entity |
| Predicate | decisionToIncludeYear |
P2233
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Olympic Games rugby sevens tournament, decisionToIncludeYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionToIncludeYear Context triple: [Olympic Games rugby sevens tournament, decisionToIncludeYear, 2009]
-
A.
includesYear
Indicates that one entity contains, references, or is associated with a specific calendar year as part of its information or scope.
-
B.
doesNotIncludeYear
Indicates that something is specified or presented without including a year component.
-
C.
selectionYear
Indicates the year in which an entity was chosen or selected for a particular role, status, or inclusion.
-
D.
optionalYearBefore
Indicates that one entity may, but does not necessarily, occur or be valid in a year that precedes the year associated with another entity.
-
E.
yearDecided
chosen
Indicates the specific calendar year in which a decision, ruling, or resolution was formally made or finalized.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 9:14 p.m.