Triple
T37742210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir |
E940745
|
entity |
| Predicate | firstFlightEngineer |
P198672
|
FINISHED |
| Object | Vladimir Solovyov |
E452493
|
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: Vladimir Solovyov | Statement: [Mir, firstFlightEngineer, Vladimir Solovyov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightEngineer Context triple: [Mir, firstFlightEngineer, Vladimir Solovyov]
-
A.
flightEngineer
Indicates that one entity serves as a flight engineer for another entity (such as a mission, aircraft, or crew).
-
B.
firstFlightCommander
Indicates that one entity served as the first commander in charge of another entity’s inaugural flight.
-
C.
firstFlightCrew
chosen
Indicates that the subject is a member of the crew on the first flight of the referenced aircraft, mission, or service.
-
D.
flightEngineerNationality
Indicates that a person serving as a flight engineer has a specified national affiliation or citizenship.
-
E.
flightMechanic
Indicates that one entity serves as a mechanic responsible for maintaining or repairing the aircraft associated with another entity.
- F. None of above.
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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40d68b97148190bb8c32ef52c04166 |
completed | June 28, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.