Triple
T33729401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Man's Folly |
E864230
|
entity |
| Predicate | containsFictionalEvent |
P143532
|
FINISHED |
| Object | charity fête |
—
|
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: charity fête | Statement: [Dead Man's Folly, containsFictionalEvent, charity fête]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFictionalEvent Context triple: [Dead Man's Folly, containsFictionalEvent, charity fête]
-
A.
hasFictionalEventType
Indicates that something is associated with, characterized by, or classified under a particular type or category of fictional event.
-
B.
associatedWithFictionalEvent
Indicates that an entity has a connection or involvement with a fictional event, such as being based on, inspired by, or participating in that imagined occurrence.
-
C.
fictionalEventMarked
Indicates that an event is identified or designated as fictional rather than real.
-
D.
hasEventInFiction
chosen
Indicates that a fictional work includes or depicts a particular event within its narrative.
-
E.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.