Triple
T28533535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Positioning System satellites |
E722101
|
entity |
| Predicate | globalSystemType |
P15304
|
FINISHED |
| Object | Global Navigation Satellite 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 Navigation Satellite System | Statement: [Global Positioning System satellites, globalSystemType, Global Navigation Satellite System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalSystemType Context triple: [Global Positioning System satellites, globalSystemType, Global Navigation Satellite System]
-
A.
rootSystemType
Indicates the type or classification of an entity’s root system (e.g., taproot, fibrous, adventitious).
-
B.
systemType
chosen
Indicates the classification or category of a system that an entity belongs to or operates as.
-
C.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
D.
systemTypeOperated
Indicates that an entity operates, controls, or runs a particular type of system.
-
E.
rackSystemType
Indicates the specific configuration or category of rack system associated with an 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fd847008190b2e0f3364ac3fedd |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:30 a.m.