Triple
T11139648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | parish church of St Mary the Virgin, Heacham |
E263505
|
entity |
| Predicate | buildingUseStatus |
P38811
|
FINISHED |
| Object | in use |
—
|
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: in use | Statement: [parish church of St Mary the Virgin, Heacham, buildingUseStatus, in use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingUseStatus Context triple: [parish church of St Mary the Virgin, Heacham, buildingUseStatus, in use]
-
A.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
B.
buildingUseAfterClosure
Indicates how a building is used or repurposed after its original function or operation has ceased.
-
C.
hasBuildingStatus
chosen
Indicates the current condition, classification, or operational state assigned to a building.
-
D.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
-
E.
buildingUseManaged
Indicates that an entity is responsible for overseeing, controlling, or administering the use or function of a building.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e860ca408190bea461e115f04fd7 |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.