Triple
T21253358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell of Inverawe |
E523800
|
entity |
| Predicate | hasHistoricSeatType |
P63119
|
FINISHED |
| Object | country house |
—
|
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: country house | Statement: [Campbell of Inverawe, hasHistoricSeatType, country house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricSeatType Context triple: [Campbell of Inverawe, hasHistoricSeatType, country house]
-
A.
hasHistoricalSeat
Indicates that an entity possesses or is associated with a historically significant seat, location, or place of authority.
-
B.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
C.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
D.
hadSeatType
chosen
Indicates that an entity was assigned or associated with a specific type or category of seat.
-
E.
hasHistoricalRegionType
Indicates that a historical region is associated with a specific type or classification of historical region.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735a0391881908e45909e939415a5 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:57 p.m.