Triple
T29323129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve |
E743565
|
entity |
| Predicate | hasFictionalTechnologyType |
P117060
|
FINISHED |
| Object | computer software |
—
|
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: computer software | Statement: [Eve, hasFictionalTechnologyType, computer software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalTechnologyType Context triple: [Eve, hasFictionalTechnologyType, computer software]
-
A.
featuresFictionalTechnology
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
-
B.
hasFictionalType
chosen
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
C.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
D.
hasFictionalProductionType
Indicates that an entity is associated with a specific type or category of fictional production (such as a genre, format, or style).
-
E.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 28, 2026, 1:24 p.m.