Triple
T32752441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Invincible |
E837532
|
entity |
| Predicate | isTranslationOfDivineName |
P176067
|
FINISHED |
| Object | Al-Aziz |
—
|
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: Al-Aziz | Statement: [The Invincible, isTranslationOfDivineName, Al-Aziz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTranslationOfDivineName Context triple: [The Invincible, isTranslationOfDivineName, Al-Aziz]
-
A.
isTranslatedBy
Indicates that one entity serves as the translator or translating agent responsible for rendering the content of another entity into a different language or form.
-
B.
containsDivineName
Indicates that the referenced entity includes or explicitly mentions a divine or sacred name within its content.
-
C.
isTranslationBy
Indicates that one entity is a translation produced by a specific agent (such as a person, system, or organization).
-
D.
hasTransliterationRole
Indicates that an entity participates in a transliteration process with a specific role (e.g., source, target, or agent of transliteration).
-
E.
eraOfTranslation
Indicates the historical period or era during which a given work was translated.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:12 a.m.