Triple
T33536810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guinness World Record for most ported video game |
E858956
|
entity |
| Predicate | holderFirstReleaseYear |
P164020
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [Guinness World Record for most ported video game, holderFirstReleaseYear, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderFirstReleaseYear Context triple: [Guinness World Record for most ported video game, holderFirstReleaseYear, 1984]
-
A.
firstSeriesYear
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
-
B.
productionStartYear
Indicates the year in which the production of an item, work, or entity first began.
-
C.
eligibleReleaseYear
Indicates the year in which something qualifies or is permitted to be released according to specified criteria or rules.
-
D.
singleReleaseYear
Indicates the year in which a particular single (song) was officially released.
-
E.
workReleaseYearOfAppearance
chosen
Indicates the year in which a particular work was first released or made its initial appearance.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:39 a.m.