Triple
T38427724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarin |
E903407
|
entity |
| Predicate | isLinkedToAncestryClaim |
P149753
|
FINISHED |
| Object | Tareen tribal lineage |
—
|
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: Tareen tribal lineage | Statement: [Tarin, isLinkedToAncestryClaim, Tareen tribal lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinkedToAncestryClaim Context triple: [Tarin, isLinkedToAncestryClaim, Tareen tribal lineage]
-
A.
alsoHasAncestry
Indicates that an entity possesses an additional ancestral lineage or heritage beyond its primary recorded ancestry.
-
B.
allegedAncestor
chosen
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
-
C.
ancestralLinks
Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
-
D.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
E.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.