Triple
T24063321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stolin |
E596014
|
entity |
| Predicate | hasAncestralCenterOf |
P137425
|
FINISHED |
| Object | Karlin-Stolin Hasidic dynasty |
—
|
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: Karlin-Stolin Hasidic dynasty | Statement: [Stolin, hasAncestralCenterOf, Karlin-Stolin Hasidic dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralCenterOf Context triple: [Stolin, hasAncestralCenterOf, Karlin-Stolin Hasidic dynasty]
-
A.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
B.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
C.
isAncestralVillageOf
chosen
Indicates that one place is the original home or traditional village from which another person, family, or community traces its ancestry.
-
D.
hasAncestralIsland
Indicates that an entity has a specific island from which its ancestors originated or to which its lineage is historically tied.
-
E.
hasLatinHierarchyCenter
Indicates that an entity has a central or primary position within a Latin-based hierarchical structure.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5825548190b94cb6e708617a7d |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:39 p.m.