Triple
T24689546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Joseph |
E611393
|
entity |
| Predicate | isMaleLineMemberOf |
P77522
|
FINISHED |
| Object | House of Habsburg |
—
|
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: House of Habsburg | Statement: [Karl Joseph, isMaleLineMemberOf, House of Habsburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMaleLineMemberOf Context triple: [Karl Joseph, isMaleLineMemberOf, House of Habsburg]
-
A.
patriarchIsMemberOf
Indicates that a patriarch belongs to or is included as a member within a particular group, organization, or entity.
-
B.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
C.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
D.
hasMemberFather
Indicates that an entity is a member of a group or organization by virtue of their father’s membership or paternal relationship.
-
E.
hasLineageMember
chosen
Indicates that one entity is a member or descendant within the lineage or ancestral line of 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:19 a.m.