Triple
T38342664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston City Hall |
E1041449
|
entity |
| Predicate | convertedToCityHallYear |
P192195
|
FINISHED |
| Object | 1818 |
—
|
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: 1818 | Statement: [Charleston City Hall, convertedToCityHallYear, 1818]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToCityHallYear Context triple: [Charleston City Hall, convertedToCityHallYear, 1818]
-
A.
convertedToCourthouse
Indicates that something has been transformed, repurposed, or changed in function to become a courthouse.
-
B.
usedAsCityHallUntil
Indicates that a building or location functioned as the city hall up to a specified end date or time period.
-
C.
usedAsCityHallFrom
Indicates that a building or location functioned as the official city hall of a municipality during a specified time period.
-
D.
hasCityHall
Indicates that a location or administrative area possesses or is served by a specific city hall building or institution.
-
E.
cityHallOf
Indicates that one entity serves as the official city hall building or administrative center for the specified city.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:30 p.m.