Triple
T23157013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawford Long |
E578467
|
entity |
| Predicate | performedFirstEtherAnesthesiaOn |
P151142
|
FINISHED |
| Object | 1842-03-30 |
—
|
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: 1842-03-30 | Statement: [Crawford Long, performedFirstEtherAnesthesiaOn, 1842-03-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedFirstEtherAnesthesiaOn Context triple: [Crawford Long, performedFirstEtherAnesthesiaOn, 1842-03-30]
-
A.
wasPioneeredInSurgeryBy
Indicates that a particular surgical technique, procedure, or approach was first developed, introduced, or trailblazed by a specific surgeon or surgical team.
-
B.
firstPerformedUnder
Indicates that an action, work, or performance was first carried out under the authority, direction, or auspices of a particular person, group, or organization.
-
C.
operatedInTheatre
Indicates that a medical or surgical procedure was performed on a patient within an operating theatre or surgical suite.
-
D.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on another entity.
-
E.
operatedTo
Indicates that one entity has performed a surgical or medical operation on another entity.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efe1b0081908e81b757d64c067c |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:01 p.m.