Triple
T2860500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voskhod spacecraft |
E63306
|
entity |
| Predicate | reentryControl |
P43711
|
FINISHED |
| Object | automatic and manual systems |
—
|
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: automatic and manual systems | Statement: [Voskhod spacecraft, reentryControl, automatic and manual systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryControl Context triple: [Voskhod spacecraft, reentryControl, automatic and manual systems]
-
A.
reentryProfile
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
B.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
C.
reentryVehicle
Indicates that an entity functions as a vehicle designed to re-enter an atmosphere from space.
-
D.
hasEntranceControl
Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
-
E.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf8c676c8190ab29f89d50bd09c3 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdee94c2081908e5075e87e70780a |
completed | March 7, 2026, 8:16 a.m. |
Created at: March 6, 2026, 10:02 p.m.