Triple
T32764629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paleo-Hebrew script |
E837856
|
entity |
| Predicate | replacedInUseForHebrewBy |
P193895
|
FINISHED |
| Object | Aramaic script |
—
|
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: Aramaic script | Statement: [Paleo-Hebrew script, replacedInUseForHebrewBy, Aramaic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedInUseForHebrewBy Context triple: [Paleo-Hebrew script, replacedInUseForHebrewBy, Aramaic script]
-
A.
correspondsToInHebrew
Indicates that one entity is the Hebrew-language equivalent or counterpart of another entity.
-
B.
transliteratedAsInModernIsraeliUsage
Indicates that one entity is the modern Israeli Hebrew transliteration form used to represent the other entity.
-
C.
oftenRenderedFromHebrewTerm
Indicates that one term is frequently used as the translation or rendering of a corresponding term originating from Hebrew.
-
D.
romanizationStandardReplacedBy
Indicates that one system or convention for romanization has been superseded and replaced by another romanization standard.
-
E.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
- F. None of above. chosen
Provenance (4 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
| PDg | Predicate description generation | batch_69fd592cc56081908ce456114d407616 |
completed | May 8, 2026, 3:31 a.m. |
Created at: May 1, 2026, 1:13 a.m.