Triple
T26753269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ceremonial county of Rutland |
E674599
|
entity |
| Predicate | containsCivilParish |
P178050
|
FINISHED |
| Object | Oakham |
—
|
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: Oakham | Statement: [ceremonial county of Rutland, containsCivilParish, Oakham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCivilParish Context triple: [ceremonial county of Rutland, containsCivilParish, Oakham]
-
A.
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.
-
B.
hasCivilParishComponent
chosen
Indicates that an entity includes or is composed of the specified civil parish as one of its administrative components.
-
C.
hasCivilParishName
Indicates that an entity has a specific civil parish name as its designated official name at the civil parish level.
-
D.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
E.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 3:54 a.m.