Triple
T7260579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Chittick |
E159639
|
entity |
| Predicate | hasTranslated |
P75990
|
FINISHED |
| Object | works of Ibn Arabi |
—
|
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: works of Ibn Arabi | Statement: [William Chittick, hasTranslated, works of Ibn Arabi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTranslated Context triple: [William Chittick, hasTranslated, works of Ibn Arabi]
-
A.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
B.
hasWorkTranslatedInto
Indicates that a work has been translated into a specified language or target work.
-
C.
laterTranslatedAs
Indicates that something was translated at a later time into a different language, form, or version under a specified title or expression.
-
D.
hasTranslationNote
Indicates that there is an explanatory note about how something has been translated, such as clarifying wording choices, alternatives, or translation issues.
-
E.
languageTranslatedFrom
Indicates that a language is the source/original language from which content has been translated into another language.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb06acd881908a1735fbbbd5756f |
completed | March 27, 2026, 8:39 p.m. |
Created at: March 27, 2026, 2:57 p.m.