Triple
T14176479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Fransokyo |
E351344
|
entity |
| Predicate | hasTechnologyLevelInFiction |
P2086
|
FINISHED |
| Object | futuristic |
—
|
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: futuristic | Statement: [San Fransokyo, hasTechnologyLevelInFiction, futuristic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTechnologyLevelInFiction Context triple: [San Fransokyo, hasTechnologyLevelInFiction, futuristic]
-
A.
featuresFictionalTechnology
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
-
B.
technologyLevel
chosen
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
C.
inUniverseTechnologyOf
Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given entity.
-
D.
inUniverseTechnologyDeveloped
Indicates that a specific technology has been created or developed within the context of a particular fictional or defined universe.
-
E.
hasFeatureInFiction
Indicates that a fictional work includes or portrays a particular feature, trait, or characteristic.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61c76e8081909994b95b631100e9 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:02 a.m.