Triple
T4248654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Zahrawi |
E95788
|
entity |
| Predicate | majorContribution |
P477
|
FINISHED |
| Object | standardization of surgical instruments |
—
|
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: standardization of surgical instruments | Statement: [Al-Zahrawi, majorContribution, standardization of surgical instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorContribution Context triple: [Al-Zahrawi, majorContribution, standardization of surgical instruments]
-
A.
notableContribution
chosen
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
-
B.
majorImpact
Indicates that one entity has a significant, highly influential, or transformative effect on another entity or outcome.
-
C.
majorImport
Indicates that one entity is a primary or significant source of imported goods or resources for another entity.
-
D.
notableContributionField
Indicates the field or domain in which an entity has made a significant or noteworthy contribution.
-
E.
majorUse
Indicates that something serves as the primary or most significant use or application of an 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9df10881908a2f039773f8afaa |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.