Triple
T27341027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Galloway |
E690098
|
entity |
| Predicate | linkedToFamilySeatArea |
P32085
|
FINISHED |
| Object | Minnigaff |
—
|
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: Minnigaff | Statement: [Earl of Galloway, linkedToFamilySeatArea, Minnigaff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToFamilySeatArea Context triple: [Earl of Galloway, linkedToFamilySeatArea, Minnigaff]
-
A.
hasFamilySeatNear
Indicates that an entity’s principal family residence or ancestral seat is located in the vicinity of another specified place or entity.
-
B.
laterFamilySeat
Indicates that one entity serves as a subsequent or later seat, residence, or base for a particular family or lineage, following an earlier one.
-
C.
familySeatFunction
Indicates that a location serves as the principal seat, residence, or base associated with a particular family or lineage.
-
D.
familySeatRegion
chosen
Indicates the region in which a family's principal seat, base, or ancestral home is located.
-
E.
familySeat
Indicates the traditional principal residence or ancestral home associated with a particular family or lineage.
- 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 11:42 a.m.