Triple
T26701304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPH4 |
E673161
|
entity |
| Predicate | fictionalRisk |
P60749
|
FINISHED |
| Object | instability |
—
|
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: instability | Statement: [CPH4, fictionalRisk, instability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalRisk Context triple: [CPH4, fictionalRisk, instability]
-
A.
hasRiskInFiction
chosen
Indicates that a subject is associated with a potential danger, threat, or harmful outcome within a fictional or narrative context.
-
B.
fictionalOutcome
Indicates that an event, action, or situation leads to a result that occurs only within a fictional, imagined, or non-real context.
-
C.
fictionalSecurityLevel
Indicates the degree or category of security status assigned within a fictional or imagined context.
-
D.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
-
E.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 3:31 a.m.