Triple
T37514730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skatsimi mage clan |
E932605
|
entity |
| Predicate | fictiveStatus |
P14491
|
FINISHED |
| Object | fictional |
—
|
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: fictional | Statement: [Skatsimi mage clan, fictiveStatus, fictional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictiveStatus Context triple: [Skatsimi mage clan, fictiveStatus, fictional]
-
A.
fictionalStatus
chosen
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
-
B.
fictionalBirthStatus
Indicates the relationship between an entity and its status of being born or created within a fictional or imaginary context.
-
C.
fictionalMaritalStatus
Indicates that an entity has a marital status that exists only within a fictional, narrative, or hypothetical context rather than in real life.
-
D.
fictionalOrphanStatus
Indicates that an entity is characterized as an orphan within a fictional or narrative context.
-
E.
stateInFiction
Indicates that a particular state or condition exists within a fictional context or narrative world rather than in real-world actuality.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 3, 2026, 4:17 p.m.