Triple
T27123648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore |
E687063
|
entity |
| Predicate | hasBuildingCodeEmphasis |
P117949
|
FINISHED |
| Object | wind-resistant construction |
—
|
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: wind-resistant construction | Statement: [Moore, hasBuildingCodeEmphasis, wind-resistant construction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingCodeEmphasis Context triple: [Moore, hasBuildingCodeEmphasis, wind-resistant construction]
-
A.
hasBuildingCodeConcern
chosen
Indicates that one entity has a concern, issue, or consideration related to building codes in connection with another entity or context.
-
B.
buildingCode
Indicates that a building is identified or classified by a specific code or designation.
-
C.
followsBuildingCode
Indicates that one entity complies with or adheres to the building code standards established by another governing authority or regulatory framework.
-
D.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
E.
hasBuildingPattern
Indicates that an entity exhibits or follows a particular architectural or structural building pattern.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 9 a.m.