Triple
T14595329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Oultremont |
E342545
|
entity |
| Predicate | estateTypeHistorically |
P114979
|
FINISHED |
| Object | rural estates |
—
|
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: rural estates | Statement: [House of Oultremont, estateTypeHistorically, rural estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estateTypeHistorically Context triple: [House of Oultremont, estateTypeHistorically, rural estates]
-
A.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
B.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
C.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
D.
historicallyAssociatedHouse
Indicates that there is a historical connection or association between an entity and a particular house, such as residence, ownership, or significant events tied to that location.
-
E.
countryHouseType
Indicates the type or category of house associated with or characteristic of a particular 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43581348190b5362251c3a89654 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.