Triple
T35094818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maison Vauquer |
E1012838
|
entity |
| Predicate | housesCharacter |
P49491
|
FINISHED |
| Object | Jean-Joachim Goriot |
—
|
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: Jean-Joachim Goriot | Statement: [Maison Vauquer, housesCharacter, Jean-Joachim Goriot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housesCharacter Context triple: [Maison Vauquer, housesCharacter, Jean-Joachim Goriot]
-
A.
houseRole
Indicates the functional role, purpose, or use that a house has within a given context or system.
-
B.
houseOrFamily
chosen
Indicates that two entities are related through a shared house, household, or family membership.
-
C.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
D.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
E.
houseHead
Indicates that one entity serves as the head, leader, or primary authority of a particular house or household associated with the other 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.