Triple
T28666670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Gray |
E725602
|
entity |
| Predicate | residesUnder |
P167924
|
FINISHED |
| Object | Town of Derry |
—
|
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: Town of Derry | Statement: [Bob Gray, residesUnder, Town of Derry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residesUnder Context triple: [Bob Gray, residesUnder, Town of Derry]
-
A.
livesUnder
Indicates that one entity resides beneath or is domiciled in a lower hierarchical or physical level relative to another entity.
-
B.
residesOver
Indicates that one entity lives or is situated in a position physically higher than or above another entity.
-
C.
believedToResideIn
Indicates that one entity is thought or assumed to live or be located in a particular place or region, without confirming this as a verified fact.
-
D.
hostResidenceOf
Indicates that a location serves as the primary place of residence for a specified person or group.
-
E.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 5:01 a.m.