Triple
T14096152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | باب الأسباط |
E339257
|
entity |
| Predicate | يتميز ب |
P662
|
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.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
benefitCharacteristic
Indicates that one entity possesses a quality or feature that provides an advantage, usefulness, or positive effect to another entity.
-
C.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
D.
subjectHasCharacteristic
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
-
E.
notableTechnicalFeature
Indicates that an entity possesses a significant or distinguishing technical characteristic or capability.
- 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.