Triple
T25389199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pausiris |
E631611
|
entity |
| Predicate | nameTransliterationFrom |
P75698
|
FINISHED |
| Object | Egyptian |
—
|
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: Egyptian | Statement: [Pausiris, nameTransliterationFrom, Egyptian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameTransliterationFrom Context triple: [Pausiris, nameTransliterationFrom, Egyptian]
-
A.
transliterationName
chosen
Indicates that one entity is the transliterated form of another entity’s name from one writing system into another.
-
B.
typicalTransliterationFrom
Indicates that one string is the standard or most commonly used transliteration of another string from one writing system to another.
-
C.
formerTransliteration
Indicates that one transliteration was previously used for an entity but has since been replaced by a different transliteration.
-
D.
standardTransliteration
Indicates that one representation of text is a transliteration of another according to a recognized standard or convention.
-
E.
alternativeTransliteration
Indicates that one written form represents an alternative way of transliterating the same original text or name into another script or orthography.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5656d3a04819081b3705ee9d4fd26 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:47 p.m.