Triple
T19210464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromaque |
E480342
|
entity |
| Predicate | adaptationNotable |
P134991
|
FINISHED |
| Object | nombreuses mises en scène modernes |
—
|
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: nombreuses mises en scène modernes | Statement: [Andromaque, adaptationNotable, nombreuses mises en scène modernes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationNotable Context triple: [Andromaque, adaptationNotable, nombreuses mises en scène modernes]
-
A.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
B.
notableAdaptation
Indicates that one work is a significant adaptation or reinterpretation of another work.
-
C.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
D.
adaptationStar
Indicates that one work is an adaptation of another, with the subject being the adapted work and the object being the original source.
-
E.
adaptationBy
Indicates a relationship where one entity has been modified, transformed, or reworked by another entity into a new form or version.
- F. None of above. chosen
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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9a0d1248190953e36e44f0cafdd |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:21 p.m.