Triple
T14096126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | باب الأسباط |
E339257
|
entity |
| Predicate | اسم بديل |
P39
|
FINISHED |
| Object | باب الأسباط |
—
|
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: باب الأسباط | Statement: [باب الأسباط, اسم بديل, باب الأسباط]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: اسم بديل Context triple: [باب الأسباط, اسم بديل, باب الأسباط]
-
A.
sonAlias
Indicates that one entity is an alternative or secondary name (alias) specifically used for a son in relation to another entity.
-
B.
alsoKnownAs
chosen
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
C.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
D.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
E.
nameReusedFor
Indicates that an existing name has been used again for a different entity or instance, rather than introducing a completely new name.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb7fb3c819083266dbe7e93aaff |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.