Triple
T33141257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grimaud |
E848157
|
entity |
| Predicate | basedOnWorkForAdaptation |
P96392
|
FINISHED |
| Object | Twenty Years After |
E16742
|
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: Twenty Years After | Statement: [Grimaud, basedOnWorkForAdaptation, Twenty Years After]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnWorkForAdaptation Context triple: [Grimaud, basedOnWorkForAdaptation, Twenty Years After]
-
A.
basedOnWorkAdaptations
Indicates that one work is an adaptation derived from, or created on the basis of, another pre-existing work.
-
B.
basedOnWorkAdaptedTo
Indicates that one work is derived from and adapted based on the content, story, or elements of another pre-existing work.
-
C.
basedOnAdaptationWorkedOn
chosen
Indicates that something is derived from or created based on an adaptation that a particular agent worked on.
-
D.
workAdaptedFor
Indicates that one work has been modified or transformed to create another work specifically suited for a different medium, context, or audience.
-
E.
workedOnAdaptationOf
Indicates that one entity contributed effort or participated in creating, modifying, or producing an adaptation of another entity.
- F. None of above.
Provenance (4 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3525ba72648190a421b2340b4442ad |
completed | June 19, 2026, 11:19 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 1, 2026, 1:28 a.m.