Triple
T2350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRE Fellow |
E43
|
entity |
| Predicate | higherThan |
P278
|
FINISHED |
| Object | Member of the Institute of Radio Engineers |
—
|
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: Member of the Institute of Radio Engineers | Statement: [IRE Fellow, higherThan, Member of the Institute of Radio Engineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherThan Context triple: [IRE Fellow, higherThan, Member of the Institute of Radio Engineers]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
isComparedTo
chosen
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
C.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
upperHouse
Indicates that one entity functions as the higher or upper legislative chamber in relation to a given political or governmental system.
- 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_69a22cde80848190b62c5f556b4d62ba |
completed | Feb. 27, 2026, 11:46 p.m. |
| NER | Named-entity recognition | batch_69a23344daf8819083118bbac5f46568 |
completed | Feb. 28, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69a232e52e7c81909c072703e28e8c61 |
completed | Feb. 28, 2026, 12:12 a.m. |
Created at: Feb. 27, 2026, 11:48 p.m.