Triple
T36444272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potsdam Commercial Historic District |
E897826
|
entity |
| Predicate | hasPrimaryBuildingFunction |
P88
|
FINISHED |
| Object | retail |
—
|
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: retail | Statement: [Potsdam Commercial Historic District, hasPrimaryBuildingFunction, retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryBuildingFunction Context triple: [Potsdam Commercial Historic District, hasPrimaryBuildingFunction, retail]
-
A.
hasTypicalBuildingUse
Indicates that something is generally or normally used for a particular type of building function or purpose.
-
B.
hasPrimaryFunction
chosen
Indicates that one entity serves as the main or principal function or role of another entity.
-
C.
currentBuildingUse
Indicates the present functional purpose or activity for which a building is being used.
-
D.
isMainBuildingOf
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
E.
buildingTypeServed
Indicates the type of building that is served, supported, or catered to by a given entity or system.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.