Triple
T10743889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Macon |
E253395
|
entity |
| Predicate | buildingStock |
P95747
|
FINISHED |
| Object | historic brick commercial buildings |
—
|
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: historic brick commercial buildings | Statement: [Downtown Macon, buildingStock, historic brick commercial buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingStock Context triple: [Downtown Macon, buildingStock, historic brick commercial buildings]
-
A.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
-
C.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
D.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
E.
buildingComplex
Indicates a relationship where multiple buildings are grouped and function together as a single integrated complex.
- F. None of above. chosen
Provenance (4 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b6b4b48190bad08500fa963062 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:15 p.m.