Triple
T28105224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir John Soane family |
E710342
|
entity |
| Predicate | associatedWithMausoleumDesign |
P202787
|
FINISHED |
| Object | Sir John Soane |
—
|
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: Sir John Soane | Statement: [Sir John Soane family, associatedWithMausoleumDesign, Sir John Soane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMausoleumDesign Context triple: [Sir John Soane family, associatedWithMausoleumDesign, Sir John Soane]
-
A.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
B.
hasPartInMausoleum
Indicates that an entity is a component, section, or element contained within or forming part of a mausoleum.
-
C.
associatedWithTombDecorationStyle
Indicates a relationship where something is linked to, characterized by, or connected with a particular style of tomb decoration.
-
D.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
E.
belongsToNecropolis
Indicates that something is part of, contained within, or associated with a particular necropolis.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
| PDg | Predicate description generation | batch_6a00bb39c9c88190b82c8a8fb6489a61 |
completed | May 10, 2026, 5:07 p.m. |
Created at: April 27, 2026, 9:07 p.m.