Triple
T31435837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Grammar School, Market Harborough |
E801925
|
entity |
| Predicate | groundFloorOriginalUse |
P44316
|
FINISHED |
| Object | open market space |
—
|
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: open market space | Statement: [Old Grammar School, Market Harborough, groundFloorOriginalUse, open market space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundFloorOriginalUse Context triple: [Old Grammar School, Market Harborough, groundFloorOriginalUse, open market space]
-
A.
hasGroundFloorUse
chosen
Indicates that a building or structure is associated with a specific functional use assigned to its ground floor level.
-
B.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
-
C.
hasFloorUse
Indicates that a particular floor or level of a building is designated for a specific function, activity, or type of use.
-
D.
hasGroundFloor
Indicates that a building or structure includes a ground-level floor as part of its layout or design.
-
E.
currentBuildingUse
Indicates the present functional purpose or activity for which a building is being used.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:01 p.m.