Triple
T36963569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Cyria |
E914367
|
entity |
| Predicate | securityLevelInFiction |
P61556
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Upper Cyria, securityLevelInFiction, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityLevelInFiction Context triple: [Upper Cyria, securityLevelInFiction, high]
-
A.
fictionalSecurityLevel
chosen
Indicates the degree or category of security status assigned within a fictional or imagined context.
-
B.
safetyInFiction
Indicates that a work of fiction portrays conditions, measures, or themes related to safety, risk, or protection within its narrative world.
-
C.
securityLevelDetail
Indicates the specific classification or degree of security associated with an entity, often including nuanced or descriptive information about its protection level.
-
D.
fictionalizationLevel
Indicates the degree to which an event, account, or representation has been altered, embellished, or invented relative to factual reality.
-
E.
visibilityInFiction
Indicates how prominently or frequently an entity appears or is portrayed within a fictional work or body of fiction.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.