Triple
T31793456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 18 |
E811528
|
entity |
| Predicate | stationSegment |
P172986
|
FINISHED |
| Object | ISS US 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: ISS US Orbital Segment | Statement: [Expedition 18, stationSegment, ISS US Orbital Segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stationSegment Context triple: [Expedition 18, stationSegment, ISS US Orbital Segment]
-
A.
stationNumber
Indicates the specific station identifier or code assigned to an entity within a system or network.
-
B.
transportSegment
Indicates a distinct portion of a larger journey or route during which something or someone is transported from one point to another.
-
C.
stationName
Indicates the name assigned to a particular station in the relationship.
-
D.
stationingBasis
Indicates the underlying reason, justification, or criteria for assigning or positioning an entity at a particular location or post.
-
E.
stationType
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: April 30, 2026, 11:39 p.m.