Triple
T18497662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvant docking module |
E451989
|
entity |
| Predicate | locationInStructure |
P33705
|
FINISHED |
| Object | attached to Mir core module |
—
|
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: attached to Mir core module | Statement: [Kvant docking module, locationInStructure, attached to Mir core module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInStructure Context triple: [Kvant docking module, locationInStructure, attached to Mir core module]
-
A.
locationOfStructure
Indicates that a particular structure is situated at or occupies a specific location.
-
B.
locatedOnStructureType
Indicates that an entity is situated on or supported by a particular type of structure.
-
C.
locationInSystem
chosen
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
D.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
E.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c15dec8190941e7c7a4cdebb66 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.