Triple
T31548857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Courthouse Arts Center |
E804938
|
entity |
| Predicate | architecturalTypeOfBuildingItOccupies |
P70315
|
FINISHED |
| Object | courthouse |
—
|
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: courthouse | Statement: [Old Courthouse Arts Center, architecturalTypeOfBuildingItOccupies, courthouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalTypeOfBuildingItOccupies Context triple: [Old Courthouse Arts Center, architecturalTypeOfBuildingItOccupies, courthouse]
-
A.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
B.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
buildingTypeAtCenter
Indicates that a specific type of building is located at the central position of a given area or spatial context.
-
D.
typeOfBuildingSpace
chosen
Indicates the specific kind or category of building space that an entity represents or occupies.
-
E.
architecturalWorkType
Indicates the specific kind or category of architectural work that characterizes the relationship between entities.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 30, 2026, 10:10 p.m.