Triple
T30342531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Milestones program |
E771794
|
entity |
| Predicate | nominationsReviewedBy |
P168870
|
FINISHED |
| Object | IEEE History Committee |
—
|
NE NERFINISHED |
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: IEEE History Committee | Statement: [IEEE Milestones program, nominationsReviewedBy, IEEE History Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nominationsReviewedBy Context triple: [IEEE Milestones program, nominationsReviewedBy, IEEE History Committee]
-
A.
nominationsAnnouncedBy
Indicates that one entity publicly announces or reveals the nominations associated with another entity.
-
B.
nominationsAnnouncedOn
Indicates the date or time at which nominations for something are officially made public.
-
C.
nominationsFrom
Indicates that one entity has put forward or proposed another entity as a candidate for a position, award, or recognition.
-
D.
nominationReceivedBy
Indicates that an entity has received a nomination from another entity or source.
-
E.
nominatedIn
Indicates that an entity has been formally put forward as a candidate for an award, position, or recognition within a specific event, context, or time period.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682046608819091b68c1f04f8f7fe |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:55 p.m.