Triple
T1784105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresnel zone plate |
E39351
|
entity |
| Predicate | focusesBy |
P32359
|
FINISHED |
| Object | constructive interference |
—
|
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: constructive interference | Statement: [Fresnel zone plate, focusesBy, constructive interference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesBy Context triple: [Fresnel zone plate, focusesBy, constructive interference]
-
A.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
focusesOnTeam
Indicates that the subject directs attention, effort, or priority toward a particular team as the main area of concern or activity.
-
C.
brandFocus
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
D.
titleIFocus
Indicates that a work’s primary or central focus is expressed or summarized by the given title.
-
E.
branchOfServiceFocus
Indicates that one entity is the primary military or organizational branch of service emphasized, specialized in, or targeted by 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab75444d28819091c393e62fc97f82 |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:31 p.m.