Triple
T6827877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El hacedor |
E157060
|
entity |
| Predicate | hasMetafictionalDevice |
P23847
|
FINISHED |
| Object | author as character |
—
|
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: author as character | Statement: [El hacedor, hasMetafictionalDevice, author as character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetafictionalDevice Context triple: [El hacedor, hasMetafictionalDevice, author as character]
-
A.
hasMetafictionalRole
Indicates that an entity plays a role within a story that self-consciously comments on, references, or breaks the conventions of fiction itself.
-
B.
hasNarrativeDevice
chosen
Indicates that one entity employs, contains, or is characterized by a particular narrative device used in storytelling or discourse.
-
C.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
D.
hasPoeticDevice
Indicates that one entity (typically a text or passage) employs or contains a specific poetic device present in the other entity.
-
E.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6254bd88190a2a424537c2c12e2 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.