Triple
T14270029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharq |
E353754
|
entity |
| Predicate | commonTransliteration |
P45745
|
FINISHED |
| Object | Sharq |
—
|
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: Sharq | Statement: [Sharq, commonTransliteration, Sharq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonTransliteration Context triple: [Sharq, commonTransliteration, Sharq]
-
A.
commonTransliterationSystem
chosen
Indicates that two or more written forms are derived using the same standardized system for converting text from one script to another.
-
B.
standardTransliteration
Indicates that one representation of text is a transliteration of another according to a recognized standard or convention.
-
C.
alternativeTransliteration
Indicates that one written form represents an alternative way of transliterating the same original text or name into another script or orthography.
-
D.
formerTransliteration
Indicates that one transliteration was previously used for an entity but has since been replaced by a different transliteration.
-
E.
transliterationName
Indicates that one entity is the transliterated form of another entity’s name from one writing system into another.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de657fe6708190b41de48c43cff647 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.