Triple
T7401970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bara'ah |
E170769
|
entity |
| Predicate | notablyLacks |
P14452
|
FINISHED |
| Object | basmala at its beginning |
—
|
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: basmala at its beginning | Statement: [Bara'ah, notablyLacks, basmala at its beginning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablyLacks Context triple: [Bara'ah, notablyLacks, basmala at its beginning]
-
A.
notableAbsence
chosen
Indicates that something or someone is conspicuously missing from a context where their presence would normally be expected or significant.
-
B.
lacksNotabilityAs
Indicates that one entity is considered insufficiently notable or significant to be associated with or classified as the other entity.
-
C.
typicallyLack
Indicates that one entity is characteristically or usually without, or does not possess, another entity or attribute.
-
D.
notablyBorneBy
Indicates that something is especially or prominently carried, supported, or borne by a particular entity, in a way that is distinctive or noteworthy.
-
E.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.