Triple
T2962820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab 340 AEW&C |
E80086
|
entity |
| Predicate | missionCrewStations |
P45255
|
FINISHED |
| Object | multiple operator consoles |
—
|
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: multiple operator consoles | Statement: [Saab 340 AEW&C, missionCrewStations, multiple operator consoles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionCrewStations Context triple: [Saab 340 AEW&C, missionCrewStations, multiple operator consoles]
-
A.
spaceStationVisit
Indicates that an entity travels to and spends time at a space station as a visitor or temporary occupant.
-
B.
notableAstronautUser
Indicates that the user has a notable or distinguished status specifically as an astronaut.
-
C.
spaceAgencyCustomer
Indicates a relationship where one entity is a customer that purchases or contracts services from a space agency.
-
D.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
-
E.
crewOfVoskhod1
Indicates the relationship of being a member of the crew assigned to the Voskhod 1 space mission.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9957602c819089b673966fd619e0 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad98379fac8190a4dfe530787703c9 |
completed | March 8, 2026, 3:39 p.m. |
Created at: March 8, 2026, 2:57 p.m.