Triple
T38576690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smythe family |
E929423
|
entity |
| Predicate | historicResidence |
P180922
|
FINISHED |
| Object | Methven Castle |
E272701
|
NE 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: Methven Castle | Statement: [Smythe family, historicResidence, Methven Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicResidence Context triple: [Smythe family, historicResidence, Methven Castle]
-
A.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
B.
historicResident
chosen
Indicates that an entity lived or resided in a place during a historically significant period or in the past.
-
C.
historicLocation
Indicates that an entity is situated in or associated with a place of historical significance.
-
D.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
E.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
- F. None of above.
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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02fb5ca96081908ff618f560011940 |
completed | May 12, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a421bd4db7481908f266dee647979dd |
completed | June 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_6a02f9602b308190a97f81821e12b13f |
completed | May 12, 2026, 9:56 a.m. |
Created at: May 3, 2026, 4:32 p.m.