Triple
T29341325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GrimE |
E744043
|
entity |
| Predicate | notableTitleReleaseYear |
P204198
|
FINISHED |
| Object | Grim Fandango (1998) |
E202713
|
NE 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: Grim Fandango (1998) | Statement: [GrimE, notableTitleReleaseYear, Grim Fandango (1998)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTitleReleaseYear Context triple: [GrimE, notableTitleReleaseYear, Grim Fandango (1998)]
-
A.
notableEditionYear
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
-
B.
EuroTitleYear
Indicates the year in which an entity received or held a specific European title or championship.
-
C.
notableTitleAssociation
Indicates an association where an entity is linked to a distinguished or noteworthy title, role, or honor it holds or has held.
-
D.
notableProductionYear
Indicates the year in which an entity produced something considered notable or significant.
-
E.
notableTitleType
Indicates that a title associated with an entity is of a type considered notable or especially significant.
- F. None of above. chosen
Provenance (5 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a0346b487088190814e4bd0765cb609 |
completed | May 12, 2026, 3:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2742f6f0488190b0a48e92c7b0047c |
completed | June 8, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_6a0346428c60819090e5ea815c0921ca |
completed | May 12, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_6a0346b3b2708190b713ce3dfee1734a |
completed | May 12, 2026, 3:26 p.m. |
Created at: April 28, 2026, 1:34 p.m.