Triple
T28168636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chirac family |
E715394
|
entity |
| Predicate | hasParentChildRelation |
P59830
|
FINISHED |
| Object | Jacques Chirac – Claude Chirac |
—
|
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: Jacques Chirac – Claude Chirac | Statement: [Chirac family, hasParentChildRelation, Jacques Chirac – Claude Chirac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentChildRelation Context triple: [Chirac family, hasParentChildRelation, Jacques Chirac – Claude Chirac]
-
A.
hasParentChildDynamicWith
Indicates a relationship in which one entity assumes a parental role and the other assumes a child role, involving hierarchical care, guidance, or authority dynamics between them.
-
B.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
C.
isParentOf
chosen
Indicates that one entity is the biological or legal parent of another entity.
-
D.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
E.
sometimesHasParent
Indicates that an entity has a particular parent entity in some, but not necessarily all, situations or contexts.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 27, 2026, 10:11 p.m.