Triple
T23443106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvercops |
E565455
|
entity |
| Predicate | isFictionalWithinWork |
P116013
|
FINISHED |
| Object | Solar Opposites |
—
|
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: Solar Opposites | Statement: [Silvercops, isFictionalWithinWork, Solar Opposites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFictionalWithinWork Context triple: [Silvercops, isFictionalWithinWork, Solar Opposites]
-
A.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
-
B.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
C.
isFictionalCharacter
chosen
Indicates that the subject is a character that exists only in fiction rather than in real life.
-
D.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
-
E.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64654e88190b530958b27b32412 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:51 p.m.