Triple
T34508344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephraim McDowell |
E885948
|
entity |
| Predicate | yearOfNotableSurgery |
P195509
|
FINISHED |
| Object | 1809 |
—
|
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: 1809 | Statement: [Ephraim McDowell, yearOfNotableSurgery, 1809]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfNotableSurgery Context triple: [Ephraim McDowell, yearOfNotableSurgery, 1809]
-
A.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
B.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on another entity.
-
C.
wasPioneeredInSurgeryBy
Indicates that a particular surgical technique, procedure, or approach was first developed, introduced, or trailblazed by a specific surgeon or surgical team.
-
D.
operatedInTheatre
Indicates that a medical or surgical procedure was performed on a patient within an operating theatre or surgical suite.
-
E.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: May 1, 2026, 2:01 a.m.