Triple
T12388680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lettres écrites de la montagne |
E295934
|
entity |
| Predicate | workSequence |
P59025
|
FINISHED |
| Object | follows the condemnation of Émile |
—
|
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: follows the condemnation of Émile | Statement: [Lettres écrites de la montagne, workSequence, follows the condemnation of Émile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSequence Context triple: [Lettres écrites de la montagne, workSequence, follows the condemnation of Émile]
-
A.
sequenceInWork
chosen
Indicates that one work appears as a sequential part or installment within a larger overarching work.
-
B.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
C.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
D.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fcf6aa8819080c9a2407a72db2e |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.