Triple
T24547468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bravonium |
E607263
|
entity |
| Predicate | modernCivilParish |
P56571
|
FINISHED |
| Object | Leintwardine |
—
|
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: Leintwardine | Statement: [Bravonium, modernCivilParish, Leintwardine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCivilParish Context triple: [Bravonium, modernCivilParish, Leintwardine]
-
A.
formerCivilParish
Indicates that an entity was once designated as a civil parish but no longer holds that administrative status.
-
B.
civilParishIn
chosen
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
C.
onlyCivilParishOf
Indicates that one entity is the sole civil parish associated with, or contained within, the other entity, with no other civil parishes sharing that association.
-
D.
isHistoricParishOf
Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
-
E.
formsCivilParishWith
Indicates that two or more entities are administratively combined to constitute a single civil parish.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8caba8c819082c3bf33b6ff9cd0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.