Triple
T35094564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Duchesse de Langeais |
E1012830
|
entity |
| Predicate | workInBalzacCycle |
P106827
|
FINISHED |
| Object | La Comédie humaine |
—
|
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: La Comédie humaine | Statement: [La Duchesse de Langeais, workInBalzacCycle, La Comédie humaine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInBalzacCycle Context triple: [La Duchesse de Langeais, workInBalzacCycle, La Comédie humaine]
-
A.
cycleWithinLaComédieHumaine
chosen
Indicates that a work belongs to a specific internal cycle or sub-series within Balzac’s larger collection *La Comédie Humaine*.
-
B.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
C.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
D.
works in
Indicates that one entity performs their job or professional activities within the organization, location, or context represented by another entity.
-
E.
notablePlaceOfWork
Indicates that there is a notable or significant place where the entity has worked or been employed.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.