Triple
T34419746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petty, Inverness-shire |
E883492
|
entity |
| Predicate | historicalEstateAreaFor |
P202253
|
FINISHED |
| Object | Moray family |
—
|
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: Moray family | Statement: [Petty, Inverness-shire, historicalEstateAreaFor, Moray family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEstateAreaFor Context triple: [Petty, Inverness-shire, historicalEstateAreaFor, Moray family]
-
A.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
B.
historicalCountyArea
Indicates that an entity’s area measurement corresponds to the size of a county as it existed during a specified historical period.
-
C.
hasHistoricVillageArea
Indicates that an entity includes or is associated with an area recognized as a historic village or traditional settlement zone.
-
D.
historicalUseOfArea
Indicates how an area was used or what activities occurred there during a past period.
-
E.
originalEstateSize
Indicates the total size or extent of an estate in its initial or historically original state.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0067cde0f08190b2cd93af5f00d519 |
completed | May 10, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_6a0065820c8c8190994734433c64a30a |
completed | May 10, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_6a0067cd38bc8190a719e9d1a287cd95 |
completed | May 10, 2026, 11:11 a.m. |
Created at: May 1, 2026, 2 a.m.