Triple
T11508166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Souls’ Church, Haley Hill, Halifax |
E272838
|
entity |
| Predicate | redundancyDeclared |
P99854
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [All Souls’ Church, Haley Hill, Halifax, redundancyDeclared, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redundancyDeclared Context triple: [All Souls’ Church, Haley Hill, Halifax, redundancyDeclared, 1979]
-
A.
isRedundantWith
Indicates that one entity duplicates or overlaps the function, information, or effect of another such that one could be removed without significant loss.
-
B.
declared
Indicates that an entity formally announces, states, or proclaims something, often with official or authoritative intent.
-
C.
supportsRedundancy
Indicates that one entity provides or enables backup or failover capabilities for another to ensure continued operation if a primary component fails.
-
D.
declaredOverBy
Indicates that one entity is formally announced, proclaimed, or made known through the authority or action of another entity.
-
E.
declaredTo
Indicates that one entity formally made a statement, announcement, or assertion to another specific entity.
- F. None of above. chosen
Provenance (4 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db43a648190be859bec2fe9f43b |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.