Triple
T9739310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merida obtains a spell from a witch |
E236144
|
entity |
| Predicate | releaseYearContext |
P30914
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Merida obtains a spell from a witch, releaseYearContext, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseYearContext Context triple: [Merida obtains a spell from a witch, releaseYearContext, 2012]
-
A.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
B.
workReleaseYear
chosen
Indicates the calendar year in which a work (such as a book, film, or album) was first released or made publicly available.
-
C.
singleReleaseYear
Indicates the year in which a particular single (song) was officially released.
-
D.
recordingReleaseYear
Indicates the calendar year in which a particular recording was first released to the public.
-
E.
compositionYear
Indicates the year in which a work (such as a piece of music, art, or literature) was originally created or composed.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef43fec8190987628f401a27436 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.