Triple
T354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute of Radio Engineers |
E6
|
entity |
| Predicate | hasInfluenceOn |
P9
|
FINISHED |
| Object | development of radio broadcasting |
—
|
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: development of radio broadcasting | Statement: [Institute of Radio Engineers, hasInfluenceOn, development of radio broadcasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfluenceOn Context triple: [Institute of Radio Engineers, hasInfluenceOn, development of radio broadcasting]
-
A.
influenced
chosen
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
E.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
- 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.