Triple
T23737369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTK |
E586573
|
entity |
| Predicate | networkRTKUses |
P153477
|
FINISHED |
| Object | multiple reference stations |
—
|
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: multiple reference stations | Statement: [RTK, networkRTKUses, multiple reference stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkRTKUses Context triple: [RTK, networkRTKUses, multiple reference stations]
-
A.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
networkStatus
Indicates the current operational state or connectivity condition of a network or networked system.
-
C.
supportsGNSS
Indicates that one entity provides compatibility with or functional support for Global Navigation Satellite System (GNSS) capabilities for another entity.
-
D.
networkCoverage
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
-
E.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
- 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_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. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:10 p.m.