Triple
T32830329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fullarton |
E839668
|
entity |
| Predicate | hasNotableFamilySeatRegion |
P32085
|
FINISHED |
| Object | Ayrshire |
—
|
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: Ayrshire | Statement: [Fullarton, hasNotableFamilySeatRegion, Ayrshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFamilySeatRegion Context triple: [Fullarton, hasNotableFamilySeatRegion, Ayrshire]
-
A.
familySeatRegion
chosen
Indicates the region in which a family's principal seat, base, or ancestral home is located.
-
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.
hasFamilySeatNear
Indicates that an entity’s principal family residence or ancestral seat is located in the vicinity of another specified place or entity.
-
D.
hasRegencySeatNearby
Indicates that an entity has a regency seat located in close geographical proximity to it.
-
E.
notableSeat
Indicates that an entity holds or is associated with a seat, position, or place that is considered notable or significant in some context.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a014a0b57dc8190b04ce51156ab95fa |
completed | May 11, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_6a0149afa57c8190a83257085766d916 |
completed | May 11, 2026, 3:14 a.m. |
Created at: May 1, 2026, 1:16 a.m.