Triple
T27433618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asad ibn Khuzayma |
E690717
|
entity |
| Predicate | relativeTribalContext |
P185719
|
FINISHED |
| Object | Mudar |
—
|
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: Mudar | Statement: [Asad ibn Khuzayma, relativeTribalContext, Mudar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeTribalContext Context triple: [Asad ibn Khuzayma, relativeTribalContext, Mudar]
-
A.
nearTribalGroup
Indicates that one entity is located geographically close to a tribal group.
-
B.
ethnicOrTribalBase
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
-
C.
relationshipToTribalLaw
Indicates that one entity has a specified legal or regulatory connection, status, or relevance with respect to tribal law.
-
D.
associatedTribeLocation
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
-
E.
tribalAffiliationType
chosen
Indicates the specific type or category of tribal affiliation that characterizes the relationship between an entity and a tribe.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: April 27, 2026, 12:43 p.m.