Triple
T2636007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FACS |
E59746
|
entity |
| Predicate | usedAsSuffixTo |
P42400
|
FINISHED |
| Object | surgeon’s name |
—
|
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: surgeon’s name | Statement: [FACS, usedAsSuffixTo, surgeon’s name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSuffixTo Context triple: [FACS, usedAsSuffixTo, surgeon’s name]
-
A.
etymologySuffix
Indicates that one term functions as a suffix in the etymological formation or derivation of another term.
-
B.
usedInFullNameOf
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
-
C.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
-
D.
usedAsSurname
Indicates that something functions as a family name borne by a person or group of people.
-
E.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8e1fffc81908e4921690098c8db |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:50 p.m.