Triple
T2134000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal College of Surgeons of Edinburgh |
E46607
|
entity |
| Predicate | servesProfession |
P21587
|
FINISHED |
| Object | surgeons |
—
|
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: surgeons | Statement: [Royal College of Surgeons of Edinburgh, servesProfession, surgeons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesProfession Context triple: [Royal College of Surgeons of Edinburgh, servesProfession, surgeons]
-
A.
professionServed
chosen
Indicates that an entity has performed work or provided services in a particular profession or occupational role.
-
B.
recognizesProfession
Indicates that one entity acknowledges or identifies another entity’s professional role or occupation as such.
-
C.
portraysProfession
Indicates that one entity depicts or represents another entity in a specific profession or occupational role.
-
D.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
E.
requiredOccupationOf
Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba24004819091ffb9440e8615fa |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.