Triple
T10527378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mork |
E248340
|
entity |
| Predicate | fictionalTechnologyUsed |
P61798
|
FINISHED |
| Object | Orkan egg-shaped 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: Orkan egg-shaped spacecraft | Statement: [Mork, fictionalTechnologyUsed, Orkan egg-shaped spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalTechnologyUsed Context triple: [Mork, fictionalTechnologyUsed, Orkan egg-shaped spacecraft]
-
A.
featuresFictionalTechnology
chosen
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
-
B.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
C.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
-
D.
envisionedTechnology
Indicates that an entity has imagined, conceptualized, or planned a particular technology, typically before it exists or is realized.
-
E.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509f5ec348190875c8c877e70ba4a |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.