Triple
T4637557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hundred of Northwich |
E101569
|
entity |
| Predicate | governedBySystem |
P44469
|
FINISHED |
| Object | English hundred system |
—
|
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: English hundred system | Statement: [Hundred of Northwich, governedBySystem, English hundred system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedBySystem Context triple: [Hundred of Northwich, governedBySystem, English hundred system]
-
A.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
B.
governedThrough
Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
-
C.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
D.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
E.
governed by
chosen
Indicates that an entity is under the authority, control, or administration of another entity that makes and enforces rules or decisions for it.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a64214481908a207e8070cc7a45 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.