Triple
T25705523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydiard Tregoze, Wiltshire, England |
E644577
|
entity |
| Predicate | governedPreviouslyAs |
P76127
|
FINISHED |
| Object | civil parish |
—
|
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: civil parish | Statement: [Lydiard Tregoze, Wiltshire, England, governedPreviouslyAs, civil parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedPreviouslyAs Context triple: [Lydiard Tregoze, Wiltshire, England, governedPreviouslyAs, civil parish]
-
A.
governedByInPast
chosen
Indicates that an entity was under the rule, control, or authority of another entity during a previous time period.
-
B.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
C.
hasGovernedWith
Indicates a relationship where two or more entities have jointly exercised governing authority or shared responsibility in ruling or managing a domain or organization.
-
D.
governedAs
Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
-
E.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 21, 2026, 9:03 p.m.