Triple
T13163015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Cousin Pons |
E312773
|
entity |
| Predicate | workInLaComedieHumaine |
P106827
|
FINISHED |
| Object | late work |
—
|
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: late work | Statement: [Le Cousin Pons, workInLaComedieHumaine, late work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInLaComedieHumaine Context triple: [Le Cousin Pons, workInLaComedieHumaine, late work]
-
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.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
C.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
-
D.
La Cotinière
Indicates a locational or associative relationship involving the place named "La Cotinière," such as being situated in, originating from, or otherwise connected to that locality.
-
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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:13 p.m.