Triple
T35967358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sīrat ʿAntar |
E1040180
|
entity |
| Predicate | depictsTribe |
P87687
|
FINISHED |
| Object | Banū ʿAbs |
—
|
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: Banū ʿAbs | Statement: [Sīrat ʿAntar, depictsTribe, Banū ʿAbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsTribe Context triple: [Sīrat ʿAntar, depictsTribe, Banū ʿAbs]
-
A.
tribeCharacterization
Indicates how a tribe or tribal group is characterized or described in terms of its defining qualities, attributes, or identity.
-
B.
ethnicGroupDepicted
chosen
Indicates that a particular ethnic group is visually represented or portrayed in the subject entity (such as an image, artwork, or media item).
-
C.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
D.
tribeOrGens
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
E.
recognizedTribeIncludes
Indicates that a formally recognized tribe encompasses or includes a particular subgroup, member, or entity within its official structure or membership.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:07 p.m.