Triple
T29766622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBAS |
E753930
|
entity |
| Predicate | usesSignalFrom |
P124740
|
FINISHED |
| Object | Global Positioning System |
—
|
NE NERFINISHED |
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: Global Positioning System | Statement: [GBAS, usesSignalFrom, Global Positioning System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSignalFrom Context triple: [GBAS, usesSignalFrom, Global Positioning System]
-
A.
providesSignal
chosen
Indicates that one entity transmits or makes available a signal to another entity for communication, control, or information purposes.
-
B.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
C.
canBeSignaledBy
Indicates that one entity is capable of being triggered, notified, or activated by another entity through some form of signaling.
-
D.
sentSignalFrom
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
-
E.
canAlsoSignalVia
Indicates that one entity, in addition to its primary signaling mechanism, is capable of conveying signals or information through an alternative pathway or medium involving another entity.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 28, 2026, 8:38 p.m.