Triple
T35104538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilconquhar family |
E1013111
|
entity |
| Predicate | hereditaryTerritory |
P182526
|
FINISHED |
| Object | barony of Kilconquhar |
—
|
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: barony of Kilconquhar | Statement: [Kilconquhar family, hereditaryTerritory, barony of Kilconquhar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryTerritory Context triple: [Kilconquhar family, hereditaryTerritory, barony of Kilconquhar]
-
A.
missionTerritoryOf
Indicates that a specified territory is under the jurisdiction or scope of a particular mission.
-
B.
governedTerritory
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
-
C.
annexedTerritory
Indicates that one political entity has formally incorporated another territory into its own sovereign domain.
-
D.
countryCedingTerritory
Indicates that one country is formally transferring control or ownership of a portion of its territory to another entity.
-
E.
historicalTerritoryType
Indicates that a territory is classified according to a specific type or category it held during a historical period.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.