Triple
T8947111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Life Fellow |
E213246
|
entity |
| Predicate | lifetimeStatus |
P75165
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [IEEE Life Fellow, lifetimeStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeStatus Context triple: [IEEE Life Fellow, lifetimeStatus, yes]
-
A.
hasLifetimeStatus
chosen
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
-
B.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
-
C.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
D.
lifecycleStatus
Indicates the current phase or condition of an entity within its overall lifecycle or progression from creation to termination.
-
E.
legalStatusEnd
Indicates the point or event at which a previously valid legal status, condition, or arrangement ceases to be in effect.
- 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.