Triple
T28717183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares III crew |
E729990
|
entity |
| Predicate | missionVehicle |
P14385
|
FINISHED |
| Object | Hermes spacecraft |
—
|
NE NERFINISHED |
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: Hermes spacecraft | Statement: [Ares III crew, missionVehicle, Hermes spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionVehicle Context triple: [Ares III crew, missionVehicle, Hermes spacecraft]
-
A.
designedCrewVehicle
Indicates that an agent or entity is responsible for designing a vehicle intended to carry a crew.
-
B.
intendedCrewVehicle
chosen
Indicates that a particular vehicle is designated or planned to be used by a specific crew.
-
C.
launcherVehicleDesignation
Indicates the specific launch vehicle or rocket designation associated with an object or mission.
-
D.
reentryVehicle
Indicates that an entity functions as a vehicle designed to re-enter an atmosphere from space.
-
E.
coreLaunchVehicle
Indicates that one entity serves as the primary launch vehicle used to propel another entity (such as a payload or mission) into space.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 5:51 a.m.