Triple
T35326497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverchaolain |
E1020199
|
entity |
| Predicate | ancestralAreaOf |
P114984
|
FINISHED |
| Object | Clan Lamont |
—
|
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: Clan Lamont | Statement: [Inverchaolain, ancestralAreaOf, Clan Lamont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralAreaOf Context triple: [Inverchaolain, ancestralAreaOf, Clan Lamont]
-
A.
ancestralDomainOf
chosen
Indicates that one entity is the original or historically prior domain from which another domain is derived or descended.
-
B.
ancestralDomain
Indicates that one entity is the traditional or long-held territory or domain from which another entity originates or to which it is ancestrally connected.
-
C.
secondaryAncestralHomeland
Indicates a place that serves as an additional or subsequent ancestral homeland for a group or lineage, distinct from their primary place of origin.
-
D.
proposedAsAncestralOriginOf
Indicates that something is suggested or hypothesized to be the ancestral source or origin of something else.
-
E.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.