Triple
T36728884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Communication Station Harold E. Holt |
E907272
|
entity |
| Predicate | signalPropagation |
P107488
|
FINISHED |
| Object | ground wave |
—
|
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 wave | Statement: [Naval Communication Station Harold E. Holt, signalPropagation, ground wave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalPropagation Context triple: [Naval Communication Station Harold E. Holt, signalPropagation, ground wave]
-
A.
signalReception
Indicates the reception or detection of a transmitted signal by a receiving entity.
-
B.
signalProperty
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
C.
propagates
chosen
Indicates that something causes itself, its effects, or its characteristics to spread or be transmitted from one entity, location, or state to others.
-
D.
signalOrigin
Indicates that one entity is the source or starting point from which a signal is generated or transmitted to others.
-
E.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.