Triple
T1888227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Fellow Committee |
E41808
|
entity |
| Predicate | typeOfHonorAdministered |
P4123
|
FINISHED |
| Object | professional recognition |
—
|
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 recognition | Statement: [IEEE Fellow Committee, typeOfHonorAdministered, professional recognition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHonorAdministered Context triple: [IEEE Fellow Committee, typeOfHonorAdministered, professional recognition]
-
A.
honourType
chosen
Indicates the specific category or classification of an honour or award associated with an entity.
-
B.
militaryAward
Indicates that an entity has received or been granted a specific military honor, decoration, or award.
-
C.
highestStateHonorOf
Indicates that one entity is the most prestigious state-level honor or award conferred by the other entity.
-
D.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
E.
honoursSystemRole
Indicates that one entity respects, preserves, or correctly applies the designated system-level role of another entity or process.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb12382b481908cd26b56f8558226 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.