Triple
T6151300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Jack S. Kilby Signal Processing Medal Committee |
E137206
|
entity |
| Predicate | typeOfAwardHandled |
P8620
|
FINISHED |
| Object | technical field award |
—
|
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: technical field award | Statement: [IEEE Jack S. Kilby Signal Processing Medal Committee, typeOfAwardHandled, technical field award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAwardHandled Context triple: [IEEE Jack S. Kilby Signal Processing Medal Committee, typeOfAwardHandled, technical field award]
-
A.
appliesToAwardType
Indicates that a rule, condition, or attribute is specifically relevant or applicable to a particular type or category of award.
-
B.
awardType
Indicates the specific category or kind of award associated with an entity or event.
-
C.
isAwardedIn
Indicates that an award or honor is given or conferred within a specific event, context, or time frame.
-
D.
awardTypeOverseen
chosen
Indicates that an entity is responsible for overseeing or managing a particular type or category of award.
-
E.
typicalAwardType
Indicates the usual or most common type or category of award associated with a given entity or context.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cfcb5cc8190b998e92211810442 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.