Triple
T16257833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VMC |
E394675
|
entity |
| Predicate | hostSpacecraftBus |
P38138
|
FINISHED |
| Object | Venus Express bus |
—
|
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: Venus Express bus | Statement: [VMC, hostSpacecraftBus, Venus Express bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSpacecraftBus Context triple: [VMC, hostSpacecraftBus, Venus Express bus]
-
A.
spacecraftBus
Indicates that one entity serves as the primary structural and support platform (bus) for a spacecraft, integrating and housing its subsystems.
-
B.
hostSpacecraft
chosen
Indicates that one entity serves as the platform or carrier on which another spacecraft is mounted, accommodated, or operated.
-
C.
mainSpacecraft
Indicates that one spacecraft is designated as the primary or principal spacecraft in relation to another entity or context.
-
D.
hostSpacecraftPartner
Indicates that one entity serves as a host spacecraft for another entity in a partnership or collaborative mission arrangement.
-
E.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c1fa208190995feaeba766b45f |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.