Triple
T6327442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLONASS |
E141894
|
entity |
| Predicate | controlSegment |
P70862
|
FINISHED |
| Object | ground control 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: ground control stations | Statement: [GLONASS, controlSegment, ground control stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlSegment Context triple: [GLONASS, controlSegment, ground control stations]
-
A.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
-
B.
pilotSegment
Indicates that an entity serves as the pilot or operator responsible for controlling a specific segment of a journey, route, or operation.
-
C.
segmentChange
Indicates a change or transition from one defined segment or phase to another within a sequence or process.
-
D.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
E.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e9532081908277f10ec380a486 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:29 p.m.