Triple
T34689929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridey Murphy |
E890862
|
entity |
| Predicate | allegedResidence |
P187412
|
FINISHED |
| Object | Belfast, Ireland |
—
|
NE NERFINISHED |
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: Belfast, Ireland | Statement: [Bridey Murphy, allegedResidence, Belfast, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedResidence Context triple: [Bridey Murphy, allegedResidence, Belfast, Ireland]
-
A.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
B.
namedAfterResidenceOf
Indicates that one entity is named after the place where another entity lives or has lived.
-
C.
likelyResidence
Indicates that an entity is probably located at, lives at, or is most commonly associated with a particular place of residence.
-
D.
residencyAt
Indicates that an entity lives or has an established residence at a particular location or address.
-
E.
intendedResidence
Indicates that one entity is designated or planned to serve as the place where another entity will live or reside.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 1, 2026, 2:05 a.m.