Triple
T35551666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucien de Rubempré |
E1027378
|
entity |
| Predicate | assumedName |
P24023
|
FINISHED |
| Object | de Rubempré |
—
|
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: de Rubempré | Statement: [Lucien de Rubempré, assumedName, de Rubempré]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumedName Context triple: [Lucien de Rubempré, assumedName, de Rubempré]
-
A.
associatedName
chosen
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
B.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
C.
titleAssumedBy
Indicates that a particular title or position has been taken on or adopted by a specific entity.
-
D.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
E.
notRealNameOf
Indicates that the referenced name is not the entity’s actual or official name (e.g., it is false, fabricated, or otherwise not the real name of that 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.