Triple
T33650399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Forz family |
E862081
|
entity |
| Predicate | lastHeir |
P177468
|
FINISHED |
| Object | Aveline de Forz |
—
|
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: Aveline de Forz | Statement: [de Forz family, lastHeir, Aveline de Forz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastHeir Context triple: [de Forz family, lastHeir, Aveline de Forz]
-
A.
lastLegitimateMaleHeirOf
Indicates that one entity is the final male descendant in a legitimate line of succession or inheritance from another entity.
-
B.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
-
C.
futureHeir
Indicates that one entity is designated or expected to inherit from another entity at a future time.
-
D.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
-
E.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:42 a.m.