Triple
T35551683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucien Chardon |
E1027378
|
entity |
| Predicate | motivationForNameChange |
P2136
|
FINISHED |
| Object | desire for social advancement |
—
|
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: desire for social advancement | Statement: [Lucien Chardon, motivationForNameChange, desire for social advancement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motivationForNameChange Context triple: [Lucien Chardon, motivationForNameChange, desire for social advancement]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
adoptedNewNameDueTo
Indicates that an entity changed its original name to a new one as a result of, or in response to, another specified entity or circumstance.
-
C.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
D.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
E.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another 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_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.