Triple
T28640573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaver, Utah |
E724909
|
entity |
| Predicate | hasBuildingListedOn |
P40016
|
FINISHED |
| Object | National Register of Historic Places |
—
|
NE NERFINISHED |
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: National Register of Historic Places | Statement: [Beaver, Utah, hasBuildingListedOn, National Register of Historic Places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingListedOn Context triple: [Beaver, Utah, hasBuildingListedOn, National Register of Historic Places]
-
A.
hasListedBuilding
chosen
Indicates that an entity possesses or includes a building that is officially designated and recorded as a listed (protected) structure.
-
B.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
C.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
D.
hasBuildingUnderCare
Indicates that an entity is responsible for the maintenance, management, or oversight of a particular building.
-
E.
hasListingBoard
Indicates that an entity is associated with or features a listing board used to display available items, offers, or information.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 4:44 a.m.