Triple
T7969363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghost Host |
E185284
|
entity |
| Predicate | statusInFiction |
P13811
|
FINISHED |
| Object | ghost |
—
|
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: ghost | Statement: [Ghost Host, statusInFiction, ghost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInFiction Context triple: [Ghost Host, statusInFiction, ghost]
-
A.
fictionalStatus
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
-
B.
stateInFiction
chosen
Indicates that a particular state or condition exists within a fictional context or narrative world rather than in real-world actuality.
-
C.
narrativeStatus
Indicates the role or state of an element within a narrative, such as whether it is current, hypothetical, background, or otherwise positioned in the story’s progression.
-
D.
fictionalBirthStatus
Indicates the relationship between an entity and its status of being born or created within a fictional or imaginary context.
-
E.
hasGroundsInFiction
Indicates that something is based on, justified by, or finds its origin within fictional works or narratives.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd1c9a081909759e5bf5237204e |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.