Triple
T20341006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Extreme Ultraviolet Hitchhiker |
E495739
|
entity |
| Predicate | hostVehicleType |
P1776
|
FINISHED |
| Object | crewed spacecraft |
—
|
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: crewed spacecraft | Statement: [International Extreme Ultraviolet Hitchhiker, hostVehicleType, crewed spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostVehicleType Context triple: [International Extreme Ultraviolet Hitchhiker, hostVehicleType, crewed spacecraft]
-
A.
hostVehicle
Indicates that one entity serves as the primary or reference vehicle in relation to another entity or context.
-
B.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
intendedVehicleClass
Indicates that one entity is designed or specified to be used with, or is appropriate for, a particular class or category of vehicle.
-
D.
vehicleFamily
Indicates that two vehicles belong to the same family or category based on shared design, platform, or lineage.
-
E.
intendedVehicle
Indicates that one entity is the vehicle that another entity plans or is meant to use.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6783533a881909a12311bb9c66542 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.