Triple
T38434299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Sanhan |
E903893
|
entity |
| Predicate | hasTribalLineage |
P181394
|
FINISHED |
| Object | Qahtani Arabs |
—
|
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: Qahtani Arabs | Statement: [Al Sanhan, hasTribalLineage, Qahtani Arabs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalLineage Context triple: [Al Sanhan, hasTribalLineage, Qahtani Arabs]
-
A.
hasTribalAncestor
chosen
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
B.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
C.
hasTribeOrigin
Indicates that an entity originates from, or is ancestrally associated with, a particular tribe.
-
D.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
E.
hasRelatedTribe
Indicates that one tribe is associated or connected to another tribe in some relevant way, such as by kinship, alliance, or shared characteristics.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a006fe981488190b4287289a3327664 |
completed | May 10, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_6a006f6976ec8190ba2c04fbaa946345 |
completed | May 10, 2026, 11:43 a.m. |
Created at: May 3, 2026, 4:31 p.m.