Triple
T1739178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Purloined Letter |
E37991
|
entity |
| Predicate | fictionalTimePeriod |
P18945
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [The Purloined Letter, fictionalTimePeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalTimePeriod Context triple: [The Purloined Letter, fictionalTimePeriod, 19th century]
-
A.
fictionalEra
chosen
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
B.
fictionalAge
Indicates the age attributed to an entity within a fictional or narrative context, rather than its real-world age.
-
C.
fictionalHistoryFeature
Indicates a relationship where something is a notable element or aspect within the fictional history or backstory of another entity.
-
D.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
E.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.