Triple
T37280034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peggy Hill |
E925355
|
entity |
| Predicate | homeNeighbor |
P24618
|
FINISHED |
| Object | Gribble family |
—
|
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: Gribble family | Statement: [Peggy Hill, homeNeighbor, Gribble family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeNeighbor Context triple: [Peggy Hill, homeNeighbor, Gribble family]
-
A.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
B.
neighborCharacter
Indicates that one character is located adjacent to or next to another character in a given context.
-
C.
neighboringFamily
chosen
Indicates that one family lives next to or very close to another family, forming a direct neighborhood relationship.
-
D.
neighborDescription
Indicates that one entity is described as being located near or adjacent to another entity, typically sharing a close spatial or contextual proximity.
-
E.
petOfNeighbor
Indicates that one entity is a pet belonging to, and typically living with, another entity who is a neighbor of the reference point.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.