Triple
T24857502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleph |
E622066
|
entity |
| Predicate | ISO15919Transliteration |
P107909
|
FINISHED |
| Object | ʾālef |
—
|
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: ʾālef | Statement: [Aleph, ISO15919Transliteration, ʾālef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO15919Transliteration Context triple: [Aleph, ISO15919Transliteration, ʾālef]
-
A.
commonTransliterationSystem
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.
transliterationName
Indicates that one entity is the transliterated form of another entity’s name from one writing system into another.
-
E.
transliterationType
chosen
Indicates the specific system or method used to convert text from one writing system into another using corresponding characters.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:21 a.m.