Triple
T30746637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitáb-i-‘Ahd |
E782832
|
entity |
| Predicate | alternativeLanguage |
P12203
|
FINISHED |
| Object | Arabic phrases |
—
|
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: Arabic phrases | Statement: [Kitáb-i-‘Ahd, alternativeLanguage, Arabic phrases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeLanguage Context triple: [Kitáb-i-‘Ahd, alternativeLanguage, Arabic phrases]
-
A.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
B.
otherLanguage
chosen
Indicates that an entity has or uses an additional language distinct from its primary or main language.
-
C.
possibleLanguage
Indicates that an entity could plausibly be expressed, interpreted, or communicated in a given language.
-
D.
suffixLanguage
Indicates that one language is used as a suffix or ending element in the formation or representation of another language or linguistic expression.
-
E.
languageShift
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 8:38 p.m.