Triple
T1215629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasidism |
E26100
|
entity |
| Predicate | hasLeadershipStructure |
P396
|
FINISHED |
| Object | dynastic leadership |
—
|
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: dynastic leadership | Statement: [Hasidism, hasLeadershipStructure, dynastic leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadershipStructure Context triple: [Hasidism, hasLeadershipStructure, dynastic leadership]
-
A.
hasOrganizationalStructure
chosen
Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
-
B.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
C.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
D.
hasSocialStructure
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
E.
hasMainGoverningBody
Indicates that an entity possesses a primary official organization or authority responsible for its overall governance or decision-making.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be059c5c8190a200f09442c22334 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.