Triple
T34508356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephraim McDowell |
E885948
|
entity |
| Predicate | performedSurgeryWithout |
P87565
|
FINISHED |
| Object | anesthesia |
—
|
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: anesthesia | Statement: [Ephraim McDowell, performedSurgeryWithout, anesthesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedSurgeryWithout Context triple: [Ephraim McDowell, performedSurgeryWithout, anesthesia]
-
A.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
B.
operatedInTheatre
Indicates that a medical or surgical procedure was performed on a patient within an operating theatre or surgical suite.
-
C.
operatedWithout
chosen
Indicates that an action, process, or entity functioned or was carried out in the absence of a specified resource, condition, or participant.
-
D.
hasEmergencySurgery
Indicates that an entity undergoes or is subject to an urgent, unplanned surgical procedure in response to an acute medical condition.
-
E.
operatedTo
Indicates that one entity has performed a surgical or medical operation on another entity.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 2:01 a.m.