Triple
T34063291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kala Dandekar |
E873553
|
entity |
| Predicate | clusterRole |
P79904
|
FINISHED |
| Object | moral center of the cluster |
—
|
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: moral center of the cluster | Statement: [Kala Dandekar, clusterRole, moral center of the cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clusterRole Context triple: [Kala Dandekar, clusterRole, moral center of the cluster]
-
A.
roleInCluster
chosen
Indicates the specific function or position an entity holds within a defined group or cluster of related entities.
-
B.
registryRole
Indicates the specific function or capacity an entity holds within a registry, such as how it participates in or is responsible for registry-related activities.
-
C.
CDCRole
Indicates that one entity holds a specific role or function within a clinical data collection (CDC) context relative to another entity.
-
D.
configurationRole
Indicates the role or function an entity assumes within a particular configuration or setup.
-
E.
groupOrCluster
Indicates that multiple entities are gathered together or associated as a single group or cluster based on some shared relation or proximity.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:52 a.m.