Triple
T29152534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riggs Bank |
E738947
|
entity |
| Predicate | mainBuildingStatus |
P38811
|
FINISHED |
| Object | listed on the National Register of Historic Places |
—
|
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: listed on the National Register of Historic Places | Statement: [Riggs Bank, mainBuildingStatus, listed on the National Register of Historic Places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBuildingStatus Context triple: [Riggs Bank, mainBuildingStatus, listed on the National Register of Historic Places]
-
A.
hasBuildingStatus
chosen
Indicates the current condition, classification, or operational state assigned to a building.
-
B.
mainBuildingName
Indicates the name that is designated as the primary or main building associated with an entity.
-
C.
mainBuildingServes
Indicates that a main building provides services, functions, or support to another entity or group of entities.
-
D.
currentBuilding
Indicates that an entity is located in, associated with, or belongs to the building that is relevant in the current context.
-
E.
mainHallStatus
Indicates the current condition or operational state of the main hall in a given context.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662a65da48190adf84c9d5202fbfa |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:43 a.m.