Triple
T11871466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISS US Orbital Segment |
E282415
|
entity |
| Predicate | structuralConnection |
P62922
|
FINISHED |
| Object | connected to Russian Orbital Segment |
—
|
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: connected to Russian Orbital Segment | Statement: [ISS US Orbital Segment, structuralConnection, connected to Russian Orbital Segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralConnection Context triple: [ISS US Orbital Segment, structuralConnection, connected to Russian Orbital Segment]
-
A.
structuralAmbition
Indicates an entity’s intention or effort to change, shape, or influence an existing structure, system, or organizational framework.
-
B.
ridgeConnection
Indicates a structural relationship where one ridge is connected or linked to another ridge, forming a continuous or associated ridge feature.
-
C.
structuralControlOn
Indicates that one entity exerts structural influence or constraint over another, affecting its form, configuration, or organization.
-
D.
linkedByStructure
chosen
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
E.
integratedStructure
Indicates that multiple components are combined into a single, cohesive structure that functions as an integrated whole.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:43 p.m.