Triple
T8947113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Life Fellow |
E213246
|
entity |
| Predicate | retainsRights |
P45186
|
FINISHED |
| Object | voting rights in IEEE |
—
|
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: voting rights in IEEE | Statement: [IEEE Life Fellow, retainsRights, voting rights in IEEE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retainsRights Context triple: [IEEE Life Fellow, retainsRights, voting rights in IEEE]
-
A.
retained
Indicates that one entity keeps possession, control, or continued engagement of another entity over a period of time.
-
B.
acquiredRightsTo
Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
-
C.
protectsRight
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
-
D.
rightsInclude
chosen
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
E.
mustRetain
Indicates that an entity is required to keep or preserve another entity and is not allowed to discard, delete, or release it.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66deb8ec819087a9c5eddd24c08a |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.