Triple
T29837855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demain, dès l’aube |
E757702
|
entity |
| Predicate | subjectOfGrief |
P56982
|
FINISHED |
| Object | Léopoldine Hugo |
—
|
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: Léopoldine Hugo | Statement: [Demain, dès l’aube, subjectOfGrief, Léopoldine Hugo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfGrief Context triple: [Demain, dès l’aube, subjectOfGrief, Léopoldine Hugo]
-
A.
grievesFor
Indicates that one entity feels grief or sorrow because of the loss, suffering, or misfortune of another entity.
-
B.
mourningCause
chosen
Indicates that one entity is in a state of mourning specifically because of the other entity, which is the cause or reason for the grief.
-
C.
subjectDiedIn
Indicates that the subject died within the specified location or place.
-
D.
mourningLevel
Indicates the degree or intensity to which an entity is experiencing or expressing mourning in response to a loss.
-
E.
mourningEmphasizedBy
Indicates that one instance of mourning is made more intense, prominent, or noticeable due to the influence or presence of another factor or expression.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 5:38 p.m.