Triple
T32148550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wright Square (Savannah, Georgia) |
E821088
|
entity |
| Predicate | hasSurroundingBuildingEra |
P93743
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Wright Square (Savannah, Georgia), hasSurroundingBuildingEra, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingBuildingEra Context triple: [Wright Square (Savannah, Georgia), hasSurroundingBuildingEra, 19th century]
-
A.
containsBuildingFromCentury
chosen
Indicates that a location or area includes at least one building that originates from a specified century.
-
B.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
-
C.
containsBuildingUsedDuring
Indicates that one entity spatially contains a building that is or was used during a specified event, period, or activity.
-
D.
hasNearbyAncientCity
Indicates that one entity is located close to another entity that is classified as an ancient city.
-
E.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 12:31 a.m.