Triple
T29754780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melville Monument, St Andrew Square, Edinburgh |
E752999
|
entity |
| Predicate | designerOfColumn |
P184
|
FINISHED |
| Object | William Burn |
—
|
NE NERFINISHED |
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: William Burn | Statement: [Melville Monument, St Andrew Square, Edinburgh, designerOfColumn, William Burn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designerOfColumn Context triple: [Melville Monument, St Andrew Square, Edinburgh, designerOfColumn, William Burn]
-
A.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
B.
columnType
Indicates the specific data type assigned to a column within a table or dataset.
-
C.
columnIn
Indicates that one entity is located within or belongs to a specific column of another structured entity (such as a table or grid).
-
D.
designedByPosition
Indicates that something is created or planned by an entity identified by a particular role or job position, rather than by a specific individual.
-
E.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 7:56 p.m.