Triple
T9023483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stamford, Lincolnshire, England |
E215984
|
entity |
| Predicate | numberOfListedBuildings |
P11484
|
FINISHED |
| Object | over 600 |
—
|
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: over 600 | Statement: [Stamford, Lincolnshire, England, numberOfListedBuildings, over 600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfListedBuildings Context triple: [Stamford, Lincolnshire, England, numberOfListedBuildings, over 600]
-
A.
hasListedBuilding
Indicates that an entity possesses or includes a building that is officially designated and recorded as a listed (protected) structure.
-
B.
numberOfBuildings
chosen
Indicates the total count of buildings associated with a given entity or within a specified context.
-
C.
listedBuildingCategory
Indicates the heritage protection grade or category assigned to a building that is officially recognized as a listed structure.
-
D.
hasHeritageListedPlace
Indicates that an entity possesses or is associated with a place that is officially designated as heritage-listed.
-
E.
heritageDesignationSystem
Indicates the formal heritage classification or protection system under which an entity has been designated.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7a770081908dfe3ce3374a04ba |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.