Triple
T36412916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gadding with Ghouls |
E896928
|
entity |
| Predicate | authenticityInUniverse |
P185463
|
FINISHED |
| Object | questionable |
—
|
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: questionable | Statement: [Gadding with Ghouls, authenticityInUniverse, questionable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authenticityInUniverse Context triple: [Gadding with Ghouls, authenticityInUniverse, questionable]
-
A.
isAuthentic
Indicates that something is genuine, real, or true to its claimed origin, nature, or standard.
-
B.
activeInFictionalUniverse
Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
-
C.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
-
D.
inUniverseContinuity
Indicates that two or more works, events, or entities occur within the same fictional universe and follow a consistent shared continuity.
-
E.
followsInUniverse
Indicates that one entity chronologically or logically comes after another within a specific fictional or defined universe or continuity.
- F. None of above. chosen
Provenance (4 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.