Triple
T1782261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knickebein |
E39314
|
entity |
| Predicate | beamName |
P32327
|
FINISHED |
| Object | guidance beam |
—
|
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: guidance beam | Statement: [Knickebein, beamName, guidance beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamName Context triple: [Knickebein, beamName, guidance beam]
-
A.
beamLine
Indicates a relationship where one entity directs or projects a beam or focused line (such as light, energy, or signal) toward another entity.
-
B.
beamType
Indicates the specific kind or category of beam involved in the relationship or action.
-
C.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
D.
beamUse
Indicates the action of directing or emitting a beam (such as light, energy, or signal) from one entity toward a target or in a specific direction.
-
E.
beamlineMedium
Indicates that one entity serves as the medium or material through which a beamline passes or operates in relation to another entity.
- 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_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab74db3dbc8190ab256a4e158062b8 |
completed | March 7, 2026, 12:44 a.m. |
Created at: March 4, 2026, 7:31 p.m.