Triple
T4583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turing Award |
E88
|
entity |
| Predicate | awardingBodyType |
P303
|
FINISHED |
| Object | professional association |
—
|
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: professional association | Statement: [Turing Award, awardingBodyType, professional association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardingBodyType Context triple: [Turing Award, awardingBodyType, professional association]
-
A.
typeOfInstitution
chosen
Indicates the specific kind or category of institution that an entity belongs to or is classified as.
-
B.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
-
C.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
D.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
E.
organizationTypeOfPresenter
Indicates that the predicate specifies the type or category of organization to which the presenter belongs or that the presenter represents.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23c24b3d08190a714126292fd5479 |
completed | Feb. 28, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69a23998af288190855f0456740cbd51 |
completed | Feb. 28, 2026, 12:40 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.