Triple
T7219974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander family heirs |
E150231
|
entity |
| Predicate | hasInheritanceBasis |
P74070
|
FINISHED |
| Object | family succession laws |
—
|
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: family succession laws | Statement: [Alexander family heirs, hasInheritanceBasis, family succession laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInheritanceBasis Context triple: [Alexander family heirs, hasInheritanceBasis, family succession laws]
-
A.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
B.
losesInheritanceThrough
Indicates that one party forfeits or is disqualified from receiving an inheritance as a consequence of another specified party or condition.
-
C.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
D.
hasBasisIn
chosen
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
E.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b1a7908190bd215ffb84592e32 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:53 p.m.