Triple
T35146812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gun |
E1014861
|
entity |
| Predicate | notableFamilyOrClan |
P111063
|
FINISHED |
| Object | Clan Gunn |
E326212
|
NE 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: Clan Gunn | Statement: [Gun, notableFamilyOrClan, Clan Gunn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilyOrClan Context triple: [Gun, notableFamilyOrClan, Clan Gunn]
-
A.
notableClans
chosen
Indicates that there exists a significant or historically important clan associated with the subject.
-
B.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
-
C.
clanFamilyOf
Indicates that one entity belongs to, descends from, or is otherwise affiliated with the same clan or extended family group as another entity.
-
D.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
E.
notableLeaderFamily
Indicates that a person belongs to the family of a notable or prominent leader.
- F. None of above.
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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a5a30e963848190aba09a88d32df7aa |
completed | July 17, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.