Triple
T21424440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPS space segment |
E528516
|
entity |
| Predicate | transmitsOn |
P143920
|
FINISHED |
| Object | L1 frequency |
—
|
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: L1 frequency | Statement: [GPS space segment, transmitsOn, L1 frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmitsOn Context triple: [GPS space segment, transmitsOn, L1 frequency]
-
A.
transmittedIn
Indicates that something (such as information, a signal, or a disease) is passed or conveyed within or through a particular medium, environment, or context.
-
B.
isTransmittedBy
Indicates that something (such as information, a signal, or a disease) is passed or conveyed from one entity to another through a specified agent or medium.
-
C.
laterTransmission
Indicates that one transmission event occurs after another in time.
-
D.
currentTransmission
Indicates that a transmission is presently in progress or actively occurring between entities.
-
E.
baseTransmission
Indicates the fundamental or default mode by which something is transmitted or passed from one entity to another.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813b798c8190a379cbf6cc6e14d2 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:48 p.m.