Triple
T33085675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacAndrew |
E846631
|
entity |
| Predicate | associatedKindred |
P173551
|
FINISHED |
| Object | Clan Chattan Confederation |
E712422
|
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 Chattan Confederation | Statement: [Clan MacAndrew, associatedKindred, Clan Chattan Confederation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedKindred Context triple: [Clan MacAndrew, associatedKindred, Clan Chattan Confederation]
-
A.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
B.
associatedBeings
Indicates that two or more beings are linked or connected to each other in some relevant way.
-
C.
choseKindredOf
chosen
Indicates that one entity selected or designated another entity as a kindred, ally, or closely affiliated counterpart.
-
D.
closestLivingRelatives
Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f022b8e08190a6e268ce15e66e14 |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.