Triple
T22853619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France family |
E566418
|
entity |
| Predicate | hasMultiGenerationalLeadership |
P149987
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [France family, hasMultiGenerationalLeadership, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultiGenerationalLeadership Context triple: [France family, hasMultiGenerationalLeadership, true]
-
A.
hasSecondGenerationLeader
Indicates that an entity is led or governed by a leader belonging to its second generation of leadership.
-
B.
hasGenerations
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
C.
hadLeadershipFrom
Indicates that one entity received leadership, guidance, or direction from another entity.
-
D.
hasTribalLeadership
Indicates that an entity holds a leadership role or governing authority within a tribal group or community.
-
E.
multiGenerationOwnershipOf
Indicates that ownership of something extends across multiple generations within the same family or lineage.
- F. None of above. chosen
Provenance (4 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eba65a881908c484262c3ee5212 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:37 p.m.