Triple
T34373644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mélo |
E882227
|
entity |
| Predicate | sourceWorkYear |
P114990
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Mélo, sourceWorkYear, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceWorkYear Context triple: [Mélo, sourceWorkYear, 1929]
-
A.
workYear
Indicates the specific year or span of years during which an entity (such as a person or organization) was engaged in work or employment.
-
B.
basedOnWorkFromYear
chosen
Indicates that something is derived from, adapted from, or otherwise based on a work that originated in a specified year.
-
C.
premiereWorkYear
Indicates the year in which a work (such as a performance, film, or composition) was first premiered or publicly presented.
-
D.
studCareerStartYear
Indicates the calendar year in which a student's academic or educational career formally began.
-
E.
parentWorkReleaseYear
Indicates the calendar year in which the parent work associated with an entity was originally released.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:59 a.m.