Triple
T6115308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lennoxlove House |
E136345
|
entity |
| Predicate | countryHouseType |
P68227
|
FINISHED |
| Object | Scottish 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: Scottish country house | Statement: [Lennoxlove House, countryHouseType, Scottish country house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryHouseType Context triple: [Lennoxlove House, countryHouseType, Scottish country house]
-
A.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
B.
houseTypeLower
Indicates that one entity has a house type that is considered lower or less than another entity’s house type in some defined ordering or hierarchy.
-
C.
houseTypeUpper
Indicates that one entity specifies the broader or more general house type category to which the other entity’s house type belongs.
-
D.
houses
Indicates that one entity serves as a dwelling or shelter for another entity.
-
E.
countryEstate
Indicates that a particular estate or property is located within or belongs to a specified country.
- 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bc246e48190b4f3d52eb682aa45 |
completed | March 22, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:14 p.m.