Triple
T30815076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Duff, 1st Earl Fife |
E784752
|
entity |
| Predicate | architectOfPrincipalResidence |
P69003
|
FINISHED |
| Object | William Adam |
—
|
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 Adam | Statement: [William Duff, 1st Earl Fife, architectOfPrincipalResidence, William Adam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectOfPrincipalResidence Context triple: [William Duff, 1st Earl Fife, architectOfPrincipalResidence, William Adam]
-
A.
architectOfResidence
chosen
Indicates that one entity is the architect responsible for designing the residence associated with another entity.
-
B.
architectOfOwnedHouses
Indicates that an entity serves as the architect or designer of houses that are owned by another specified entity.
-
C.
isArchitectDesigned
Indicates that something was created or planned by a professional architect.
-
D.
ownedResidence
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
E.
roofDesignedBy
Indicates that a roof was designed or planned by a particular agent, such as an architect, designer, or organization.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 29, 2026, 8:43 p.m.