Triple
T8459109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorenz beam system |
E199994
|
entity |
| Predicate | technologyClass |
P82761
|
FINISHED |
| Object | ground-based radio navigation aid |
—
|
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: ground-based radio navigation aid | Statement: [Lorenz beam system, technologyClass, ground-based radio navigation aid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyClass Context triple: [Lorenz beam system, technologyClass, ground-based radio navigation aid]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
technologyIncludes
Indicates that one technology encompasses, contains, or incorporates another technology as part of its components, features, or implementation.
-
C.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
D.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
E.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49e036c8190abb50ca272266ca6 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:10 p.m.