Triple
T36920688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rundown pub |
E913189
|
entity |
| Predicate | hasBuildingCondition |
P25131
|
FINISHED |
| Object | peeling paint |
—
|
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: peeling paint | Statement: [Rundown pub, hasBuildingCondition, peeling paint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingCondition Context triple: [Rundown pub, hasBuildingCondition, peeling paint]
-
A.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
B.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
C.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
D.
buildingCondition
chosen
Indicates the physical state or quality of a building, such as how well it is preserved, maintained, or structurally sound.
-
E.
hasBuildingForm
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:13 p.m.