Triple
T1315056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Architects Registration Board |
E28082
|
entity |
| Predicate | publicBodyType |
P26910
|
FINISHED |
| Object | independent regulator |
—
|
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: independent regulator | Statement: [Architects Registration Board, publicBodyType, independent regulator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicBodyType Context triple: [Architects Registration Board, publicBodyType, independent regulator]
-
A.
publicBody
Indicates that an entity functions as a governmental or publicly controlled organization that performs public duties or services.
-
B.
typeOfBody
Indicates that one entity is the classification or kind of physical body that the other entity is.
-
C.
establishesBodyType
Indicates that an entity defines or sets the physical or structural body type of another entity.
-
D.
supportsBody
Indicates that one entity physically or structurally holds up, bears the weight of, or provides foundational stability for another entity’s body.
-
E.
definesBody
Indicates that one entity specifies or determines the physical structure, form, or composition of another entity’s body.
- F. None of above. chosen
Provenance (4 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1598f488190b01cf4c3f1e613a7 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfc2134c81909cbaaa151d96e9a8 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:55 p.m.