Triple
T36096154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyut 6 aft port |
E1044067
|
entity |
| Predicate | positionOnVehicle |
P3250
|
FINISHED |
| Object | aft |
—
|
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: aft | Statement: [Salyut 6 aft port, positionOnVehicle, aft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnVehicle Context triple: [Salyut 6 aft port, positionOnVehicle, aft]
-
A.
positionOnAircraft
Indicates that one entity occupies a specific seat or location on an aircraft in relation to that aircraft.
-
B.
appliedToLocationOnVehicle
Indicates that something (such as a treatment, device, or action) is applied specifically to a particular location or area on a vehicle.
-
C.
positionOn
chosen
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
positionOnSystem
Indicates the relative location or placement of an entity within a larger structured system or framework.
-
E.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: May 3, 2026, 4:08 p.m.