Triple
T17218080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saorsat |
E417902
|
entity |
| Predicate | signalFootprintDesign |
P57584
|
FINISHED |
| Object | focused on Ireland |
—
|
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: focused on Ireland | Statement: [Saorsat, signalFootprintDesign, focused on Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalFootprintDesign Context triple: [Saorsat, signalFootprintDesign, focused on Ireland]
-
A.
circuitDesigner
Indicates that an entity is responsible for designing or creating electronic circuits for another entity or system.
-
B.
hardwareDesign
Indicates a relationship where one entity is responsible for creating, specifying, or engineering the physical components and architecture of another entity’s hardware system.
-
C.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
D.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
E.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddb2b148190b3b50572cc285e3d |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.