Triple
T18613807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banu Najjar |
E454965
|
entity |
| Predicate | statusInMedina |
P132789
|
FINISHED |
| Object | prominent clan |
—
|
LITERAL FINISHED |
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: prominent clan | Statement: [Banu Najjar, statusInMedina, prominent clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInMedina Context triple: [Banu Najjar, statusInMedina, prominent clan]
-
A.
statusInMexico
Indicates the legal or social status that an entity holds within the context of Mexico.
-
B.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
C.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
D.
statusInDerna
Indicates the specific condition, role, or situation an entity holds within the context of Derna.
-
E.
statusInEgypt
Indicates the legal, social, or official condition or standing that an entity holds specifically within the context of Egypt.
- F. None of above. chosen
Provenance (4 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d03feb88190bbd8889273d82f7f |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:45 a.m.