Triple
T24380036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banu Abs |
E614581
|
entity |
| Predicate | hasNotableChieftain |
P114666
|
FINISHED |
| Object | Qays ibn Zuhayr |
—
|
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: Qays ibn Zuhayr | Statement: [Banu Abs, hasNotableChieftain, Qays ibn Zuhayr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableChieftain Context triple: [Banu Abs, hasNotableChieftain, Qays ibn Zuhayr]
-
A.
hasNotableCaptain
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
B.
hasChieftaincyStructure
Indicates that an entity possesses an organized system of traditional leadership or chieftaincy hierarchy.
-
C.
hasNotablePatriarch
Indicates that an entity is associated with a prominent or historically significant male ancestral or founding figure.
-
D.
hasNotableDukedom
Indicates that an entity holds or is associated with a dukedom that is considered historically or culturally significant.
-
E.
notableLeaderFromTribe
chosen
Indicates that a person is recognized as a prominent or distinguished leader originating from a particular 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293db31c481908484ab28921cd5fd |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.