Triple
T26598351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoddom |
E667552
|
entity |
| Predicate | hasEcclesiasticalHistory |
P98999
|
FINISHED |
| Object | medieval parish church |
—
|
LITERAL FINISHED |
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: medieval parish church | Statement: [Hoddom, hasEcclesiasticalHistory, medieval parish church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcclesiasticalHistory Context triple: [Hoddom, hasEcclesiasticalHistory, medieval parish church]
-
A.
hasEcclesiasticalHistoryPeriod
Indicates that something is associated with, belongs to, or falls within a particular period in ecclesiastical (church) history.
-
B.
hasParishHistory
chosen
Indicates that an entity possesses or is associated with a documented historical record of a parish.
-
C.
hasEcclesiasticalInfluenceIn
Indicates that an entity holds religious or church-related authority, impact, or sway within a specified region, institution, or context.
-
D.
hasEcclesiasticalChange
Indicates a change in ecclesiastical status, structure, jurisdiction, or affiliation affecting the related entities.
-
E.
hasDioceseHistory
Indicates that an entity has an associated historical record or account of its diocese, including its past developments, changes, or events.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6156db8c081909facff45ff1cda55 |
completed | May 2, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:11 a.m.