Triple
T27811411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supremacy |
E702527
|
entity |
| Predicate | fictionalVehicleIn |
P131602
|
FINISHED |
| Object | Star Wars franchise |
—
|
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: Star Wars franchise | Statement: [Supremacy, fictionalVehicleIn, Star Wars franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalVehicleIn Context triple: [Supremacy, fictionalVehicleIn, Star Wars franchise]
-
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.
vehicleDrivenInFiction
Indicates that a vehicle is depicted as being driven or operated within a fictional work or narrative.
-
C.
vehicleDeveloped
Indicates that an entity (such as a person, organization, or group) created, designed, or otherwise developed a particular vehicle.
-
D.
producedVehicle
Indicates that one entity manufactured or created a particular vehicle.
-
E.
vehicleOfTimeDisplacement
Indicates a relationship where something serves as the means or mechanism by which time displacement (time travel or temporal shifting) is carried out.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 27, 2026, 5:42 p.m.