Triple
T34297711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassandra Kopelson |
E880076
|
entity |
| Predicate | specializationContext |
P188461
|
FINISHED |
| Object | surgery |
—
|
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: surgery | Statement: [Cassandra Kopelson, specializationContext, surgery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specializationContext Context triple: [Cassandra Kopelson, specializationContext, surgery]
-
A.
contextType
Indicates the type or category of contextual information associated with an entity or event.
-
B.
standardizationContext
Indicates the context, framework, or setting within which a standardization process or activity is defined or applied.
-
C.
speciesContext
Indicates the biological or taxonomic context in which a species is situated or interpreted (e.g., its classification, environment, or relevant ecological setting).
-
D.
developedByContext
Indicates that something was developed or created within, and influenced by, a particular contextual setting or circumstances.
-
E.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
- F. None of above. chosen
Provenance (4 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 1, 2026, 1:57 a.m.