Triple
T7831170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airmyn |
E181370
|
entity |
| Predicate | churchListingGrade |
P60267
|
FINISHED |
| Object | Grade II* listed building |
—
|
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: Grade II* listed building | Statement: [Airmyn, churchListingGrade, Grade II* listed building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchListingGrade Context triple: [Airmyn, churchListingGrade, Grade II* listed building]
-
A.
hasBuildingGrade
chosen
Indicates that a building is assigned a particular grade or quality rating.
-
B.
hasListedBuilding
Indicates that an entity possesses or includes a building that is officially designated and recorded as a listed (protected) structure.
-
C.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
D.
heritageDesignationSystem
Indicates the formal heritage classification or protection system under which an entity has been designated.
-
E.
hasHeritageListedPlace
Indicates that an entity possesses or is associated with a place that is officially designated as heritage-listed.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb0647848081908d74e09f52d0919e |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:44 p.m.