Triple
T8446239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poe Cottage, Fordham, New York, United States |
E199683
|
entity |
| Predicate | PoeResidenceEnd |
P83404
|
FINISHED |
| Object | 1849 |
—
|
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: 1849 | Statement: [Poe Cottage, Fordham, New York, United States, PoeResidenceEnd, 1849]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PoeResidenceEnd Context triple: [Poe Cottage, Fordham, New York, United States, PoeResidenceEnd, 1849]
-
A.
resurrectionPlace
Indicates the location where an entity is brought back to life or restored from death.
-
B.
coffinLocation
Indicates the place where a coffin is situated or stored.
-
C.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
D.
chamberOfFinalPassage
Indicates a relationship where a location serves as the last or decisive venue through which something (such as legislation, a process, or a journey) must pass before completion or enactment.
-
E.
formerGraveOf
Indicates that a location once served as the grave of an entity, but no longer does (e.g., the remains have been moved or the grave has been removed).
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3152a3c819092efdeab718def7a |
completed | March 31, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:09 p.m.