Triple
T23737370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTK |
E586573
|
entity |
| Predicate | networkRTKProvides |
P30353
|
FINISHED |
| Object | virtual reference station corrections |
—
|
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: virtual reference station corrections | Statement: [RTK, networkRTKProvides, virtual reference station corrections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkRTKProvides Context triple: [RTK, networkRTKProvides, virtual reference station corrections]
-
A.
networkCenter
Indicates that an entity functions as the central or primary hub within a network, coordinating or connecting other nodes.
-
B.
networkStatus
Indicates the current operational state or connectivity condition of a network or networked system.
-
C.
networkServed
chosen
Indicates that a network provides connectivity or services to a particular entity or set of entities.
-
D.
routingCapability
Indicates the ability of an entity to determine and direct the path that data, messages, or items should take through a network or system.
-
E.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad356c88190ae29ce403145ee73 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:10 p.m.