Triple
T35977855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh Galut |
E1040471
|
entity |
| Predicate | hasTitleInAramaic |
P195952
|
FINISHED |
| Object | Resh Galuta |
—
|
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: Resh Galuta | Statement: [Rosh Galut, hasTitleInAramaic, Resh Galuta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleInAramaic Context triple: [Rosh Galut, hasTitleInAramaic, Resh Galuta]
-
A.
hasTitleInTransliteration
Indicates that an entity has a specific title represented in a transliterated form from another writing system.
-
B.
titleInHebrew
Indicates that an entity has a specific title expressed in the Hebrew language.
-
C.
titleInArabicScript
Indicates that an entity’s title is represented in Arabic script.
-
D.
hasTitleInEnglishOrthography
Indicates that an entity has a specific title expressed using English spelling and writing conventions.
-
E.
hasTitleInRevisedRomanization
Indicates that an entity has a specific title expressed using the Revised Romanization system for Korean.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
| PDg | Predicate description generation | batch_69fdf5cfa1ec8190b80d887fa1bfb4cf |
completed | May 8, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:07 p.m.