Triple
T32614055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson |
E833736
|
entity |
| Predicate | hasFictionalUniverseVehicle |
P131602
|
FINISHED |
| Object | USCSS Prometheus |
—
|
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: USCSS Prometheus | Statement: [Jackson, hasFictionalUniverseVehicle, USCSS Prometheus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalUniverseVehicle Context triple: [Jackson, hasFictionalUniverseVehicle, USCSS Prometheus]
-
A.
hasFictionalVehicle
chosen
Indicates that one entity possesses, controls, or is associated with a vehicle that exists only in a fictional or imaginary context.
-
B.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
C.
starVehicleFor
Indicates that one entity serves as the primary or featured vehicle associated with another entity, such as a person, production, or event.
-
D.
studioStarVehicleFor
Indicates that a studio created or promoted a particular work primarily as a vehicle to showcase or advance a specific star performer.
-
E.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 1, 2026, 1:06 a.m.