Triple
T357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute of Radio Engineers |
E6
|
entity |
| Predicate | predecessorOf |
P97
|
FINISHED |
| Object | IEEE technical societies in communications |
—
|
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: IEEE technical societies in communications | Statement: [Institute of Radio Engineers, predecessorOf, IEEE technical societies in communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorOf Context triple: [Institute of Radio Engineers, predecessorOf, IEEE technical societies in communications]
-
A.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
C.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
D.
formerName
Indicates that an entity was previously known by a different name in the past.
-
E.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
- 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_69a222a954e48190b48f126a67485661 |
completed | Feb. 27, 2026, 11:03 p.m. |
| NER | Named-entity recognition | batch_69a228187e888190b2bb2aee9a69b61b |
completed | Feb. 27, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69a226e6f58881908808f6985f779c3c |
completed | Feb. 27, 2026, 11:21 p.m. |
Created at: Feb. 27, 2026, 11:04 p.m.