Triple
T21469500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Hohenlohe |
E529685
|
entity |
| Predicate | hasOccupationForMembers |
P112780
|
FINISHED |
| Object | military leader |
—
|
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: military leader | Statement: [House of Hohenlohe, hasOccupationForMembers, military leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupationForMembers Context triple: [House of Hohenlohe, hasOccupationForMembers, military leader]
-
A.
hasMemberWhoHeldOccupation
chosen
Indicates that a group or collective entity includes at least one member who has held a specified occupation.
-
B.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
C.
requiredOccupationOf
Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
-
D.
hasOccupationOfDesignee
Indicates that one entity serves as the designated or appointed holder of an occupation or role for another entity.
-
E.
siblingOccupation
Indicates that one person has a sibling whose job or profession is the specified occupation.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea12d9048190bf51ca3efc435a64 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:16 p.m.