Triple
T36333801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Range Navigation |
E894724
|
entity |
| Predicate | LORAN-CStandardFrequency |
P48082
|
FINISHED |
| Object | 100 kHz |
—
|
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: 100 kHz | Statement: [Long Range Navigation, LORAN-CStandardFrequency, 100 kHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LORAN-CStandardFrequency Context triple: [Long Range Navigation, LORAN-CStandardFrequency, 100 kHz]
-
A.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
B.
hasBroadcastFrequency
chosen
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
C.
ParisAirShowFrequency
Indicates how often the Paris Air Show event takes place over a given period.
-
D.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
E.
hasFrequencyChannels
Indicates that an entity is associated with, or operates over, one or more specific frequency channels.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.