Triple
T7306009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habsburg archduchesses |
E167975
|
entity |
| Predicate | hereditaryNature |
P66160
|
FINISHED |
| Object | title by birth or marriage |
—
|
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: title by birth or marriage | Statement: [Habsburg archduchesses, hereditaryNature, title by birth or marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryNature Context triple: [Habsburg archduchesses, hereditaryNature, title by birth or marriage]
-
A.
hereditaryInFamily
Indicates that a trait, condition, or characteristic is passed down through generations within the same family.
-
B.
geneticInfluence
Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
-
C.
nonHereditary
Indicates that a trait, condition, or status is not passed down genetically from parents to offspring.
-
D.
hereditaryAssociation
chosen
Indicates a relationship in which a trait, condition, or characteristic is passed from ancestors to descendants through genetic inheritance.
-
E.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd7dcf88190b3e66bea327fc63d |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.