Triple
T351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute of Radio Engineers |
E6
|
entity |
| Predicate | focusPeriod |
P106
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Institute of Radio Engineers, focusPeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusPeriod Context triple: [Institute of Radio Engineers, focusPeriod, early 20th century]
-
A.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
C.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
D.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a22817db00819086e6d17b6a525bdc |
completed | Feb. 27, 2026, 11:26 p.m. |
Created at: Feb. 27, 2026, 11:04 p.m.