Triple
T23432417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georges Pontmercy |
E563366
|
entity |
| Predicate | causeOfEstrangement |
P138190
|
FINISHED |
| Object | Hostility of Marius’s royalist grandfather |
—
|
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: Hostility of Marius’s royalist grandfather | Statement: [Georges Pontmercy, causeOfEstrangement, Hostility of Marius’s royalist grandfather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfEstrangement Context triple: [Georges Pontmercy, causeOfEstrangement, Hostility of Marius’s royalist grandfather]
-
A.
reasonForDisownment
chosen
Indicates the specific cause or justification for which one party disowns or severs familial or formal ties with another.
-
B.
divorceReason
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
C.
relationshipConflictWith
Indicates a state of opposition, disagreement, or incompatibility between two entities within a relationship.
-
D.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
-
E.
causeOfBetrayal
Indicates that one entity is the reason or motivating factor behind another entity’s act of betrayal.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d920548190904f80c7c40cba06 |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:49 p.m.