Triple
T27655027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zarya Functional Cargo Block |
E696969
|
entity |
| Predicate | moduleSegment |
P150481
|
FINISHED |
| Object | Russian Orbital Segment |
—
|
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: Russian Orbital Segment | Statement: [Zarya Functional Cargo Block, moduleSegment, Russian Orbital Segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moduleSegment Context triple: [Zarya Functional Cargo Block, moduleSegment, Russian Orbital Segment]
-
A.
moduleOf
chosen
Indicates that one entity functions as a component or sub-unit that belongs to, or is contained within, another larger entity.
-
B.
moduleType
Indicates the classification or category of a module in terms of its functional or structural type.
-
C.
modernSegmentsFormPartOf
Indicates that certain modern segments constitute a component or subdivision of a larger whole.
-
D.
moduleSystem
Indicates a relationship where one entity functions as or uses a particular module system to organize, load, or manage modular components.
-
E.
moduleLevel
Indicates that something is associated with, defined at, or applicable to the module level rather than to more specific internal components.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:33 p.m.