Triple
T2503141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Pella |
E52512
|
entity |
| Predicate | hasBuildingCode |
P29233
|
FINISHED |
| Object | follows Iowa state building codes |
—
|
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: follows Iowa state building codes | Statement: [City of Pella, hasBuildingCode, follows Iowa state building codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingCode Context triple: [City of Pella, hasBuildingCode, follows Iowa state building codes]
-
A.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
B.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
C.
hasBuildingFunction
Indicates that a building is used for or serves a particular function or purpose.
-
D.
followsBuildingCode
chosen
Indicates that one entity complies with or adheres to the building code standards established by another governing authority or regulatory framework.
-
E.
hasKeyBuilding
Indicates that one entity possesses or is associated with a primary or central building related to it.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1cb4f6481908d4e0a1dc0d84d3c |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.