Triple
T12697855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hussain |
E303381
|
entity |
| Predicate | hasTransliterationBasis |
P2508
|
FINISHED |
| Object | Arabic name Husayn |
—
|
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 name Husayn | Statement: [Hussain, hasTransliterationBasis, Arabic name Husayn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransliterationBasis Context triple: [Hussain, hasTransliterationBasis, Arabic name Husayn]
-
A.
hasTransliterationType
Indicates the type or system of transliteration used to convert text from one writing system into another.
-
B.
hasTransliterationRole
Indicates that an entity participates in a transliteration process with a specific role (e.g., source, target, or agent of transliteration).
-
C.
hasTransliterationRule
Indicates that there exists a specific rule or mapping that defines how text in one script or writing system is systematically converted into another.
-
D.
hasTranslationBase
Indicates that one entity serves as the original source or base text from which the other entity is translated.
-
E.
hasRomanizationOf
chosen
Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.