Triple
T29656126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grenaby |
E750267
|
entity |
| Predicate | locatedInHistoricParish |
P101108
|
FINISHED |
| Object | Malew |
—
|
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: Malew | Statement: [Grenaby, locatedInHistoricParish, Malew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHistoricParish Context triple: [Grenaby, locatedInHistoricParish, Malew]
-
A.
isHistoricParishOf
chosen
Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
-
B.
locatedInHistoricBarony
Indicates that one entity is situated within the geographical area of a historically recognized barony.
-
C.
hasHistoricParishCharacter
Indicates that something possesses the distinctive qualities or attributes traditionally associated with a historic parish.
-
D.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
E.
historicalTownshipOf
Indicates that one entity was formerly a township encompassing or governing the other entity during a past historical period.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: April 28, 2026, 6:55 p.m.