Triple
T38092833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APAS docking system |
E951156
|
entity |
| Predicate | laterStandardizedBy |
P7897
|
FINISHED |
| Object | Russian space program |
—
|
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 space program | Statement: [APAS docking system, laterStandardizedBy, Russian space program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterStandardizedBy Context triple: [APAS docking system, laterStandardizedBy, Russian space program]
-
A.
laterStandardization
chosen
Indicates that one entity becomes standardized or formally established at a later time than another entity.
-
B.
previouslyStandardizedBy
Indicates that an entity was standardized or formally defined by another entity at some earlier time, but that standardization is no longer current.
-
C.
wasGraduallyStandardizedIn
Indicates that something became standardized or uniform within a particular context through a gradual, step-by-step process over time.
-
D.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
E.
previouslyStandardizedAs
Indicates that an entity was formerly standardized under a different name, code, or specification than the one it currently has.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a016777257081908841c5522dfa76e6 |
completed | May 11, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_6a0164e49bec8190af3c8626be9677a9 |
completed | May 11, 2026, 5:11 a.m. |
Created at: May 3, 2026, 4:21 p.m.