Triple
T26229668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Register of Architects |
E655997
|
entity |
| Predicate | controlledTitle |
P47620
|
FINISHED |
| Object | architect |
—
|
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: architect | Statement: [Register of Architects, controlledTitle, architect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledTitle Context triple: [Register of Architects, controlledTitle, architect]
-
A.
controlsTitle
Indicates that one entity has the authority or power to determine, assign, or modify the title of another entity.
-
B.
centralTitle
Indicates that one title functions as the primary or main title in relation to other associated titles.
-
C.
standardTitle
Indicates that an entity has a primary or official title or name by which it is commonly recognized.
-
D.
providedTitle
chosen
Indicates that one entity has supplied or assigned a specific title or designation to another entity.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 26, 2026, 8:59 p.m.