Triple
T4692097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pombaline architecture |
E104055
|
entity |
| Predicate | regulatoryAspect |
P32982
|
FINISHED |
| Object | strict 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: strict building codes | Statement: [Pombaline architecture, regulatoryAspect, strict building codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryAspect Context triple: [Pombaline architecture, regulatoryAspect, strict building codes]
-
A.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
B.
regulatoryField
Indicates that one entity operates within, is governed by, or is associated with a particular area or domain of regulation defined by another entity.
-
C.
regulatoryStructure
Indicates a relationship where one entity serves as a regulatory framework, mechanism, or control system that governs, constrains, or modulates the behavior or operation of another entity.
-
D.
regulatoryStandard
chosen
Indicates that one entity serves as an official rule, guideline, or benchmark that governs, constrains, or evaluates the behavior, quality, or performance of another entity.
-
E.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.