Triple
T13844807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Drummond |
E332769
|
entity |
| Predicate | hasClanSeatLocation |
P108815
|
FINISHED |
| Object | Near Crieff, Perthshire |
—
|
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: Near Crieff, Perthshire | Statement: [Clan Drummond, hasClanSeatLocation, Near Crieff, Perthshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanSeatLocation Context triple: [Clan Drummond, hasClanSeatLocation, Near Crieff, Perthshire]
-
A.
hasClanSeat
Indicates that an entity holds an official seat or position within a particular clan.
-
B.
hasClanStatus
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
-
C.
hasClanChiefStatus
Indicates that an entity holds the role or status of being the chief or leader of a clan.
-
D.
hasClanName
Indicates that an entity bears or is associated with a particular clan name.
-
E.
clanSeatArea
chosen
Indicates the geographic area or territory associated with a clan’s primary seat or base of authority.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b1a25c8190a9f85ba43c421188 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.