Triple
T25619743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | المقوم بن عبد المطلب |
E642260
|
entity |
| Predicate | بطنه |
P74790
|
FINISHED |
| Object | بنو هاشم |
—
|
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: بنو هاشم | Statement: [المقوم بن عبد المطلب, بطنه, بنو هاشم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: بطنه Context triple: [المقوم بن عبد المطلب, بطنه, بنو هاشم]
-
A.
البطن
chosen
Indicates a relationship where something is located in, contained within, or belongs to the inner part or core (literal or figurative) of something else.
-
B.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
C.
torse
Indicates a heraldic depiction where a twisted roll of fabric (the torse) encircles the top of a helmet, typically serving as the base for a crest.
-
D.
hasSupportOnStomach
Indicates that one entity provides physical support or contact specifically on the stomach area of another entity.
-
E.
bodyContour
Indicates the shape or outline of a body as defined by its external curves and boundaries.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa1f5710819086f3ba4b42b6478b |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:03 p.m.