Triple
T36096766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DM |
E1044083
|
entity |
| Predicate | locationOnMir |
P204726
|
FINISHED |
| Object | Kristall module forward port |
E1327411
|
NE 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: Kristall module forward port | Statement: [DM, locationOnMir, Kristall module forward port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnMir Context triple: [DM, locationOnMir, Kristall module forward port]
-
A.
locationOnKit
Indicates that an entity is located on or attached to a specific kit or equipment set.
-
B.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
C.
mineLocation
Indicates that a specified location is the site where a particular mine (e.g., resource extraction or explosive device) is situated.
-
D.
meterLocation
Indicates the physical placement or position of a meter relative to the object or environment it is associated with.
-
E.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
- F. None of above. chosen
Provenance (5 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d54aab248190a865e10399e92f5a |
completed | June 22, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:08 p.m.