Triple
T36567226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Images, Book I |
E902010
|
entity |
| Predicate | hasMovementWithProgrammaticTitle |
P199969
|
FINISHED |
| Object | Reflets dans l’eau |
—
|
NE NERFINISHED |
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: Reflets dans l’eau | Statement: [Images, Book I, hasMovementWithProgrammaticTitle, Reflets dans l’eau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementWithProgrammaticTitle Context triple: [Images, Book I, hasMovementWithProgrammaticTitle, Reflets dans l’eau]
-
A.
hasMovementLegacy
Indicates that an entity carries forward, preserves, or significantly influences the ongoing impact, traditions, or ideals of a particular movement.
-
B.
hasTitleOver
Indicates that one entity holds a formal title, rank, or designation in relation to another entity.
-
C.
hasTitleEvent
Indicates that an entity is associated with a specific event in which a title is conferred, awarded, or formally recognized.
-
D.
hasMovementBefore
Indicates that one movement or motion event occurs earlier in time than another movement or motion event.
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
| PDg | Predicate description generation | batch_69ff659717708190bb56714d1b261063 |
completed | May 9, 2026, 4:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.