Triple
T4769007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atbash |
E105879
|
entity |
| Predicate | originCulture |
P56388
|
FINISHED |
| Object | ancient Hebrew culture |
—
|
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: ancient Hebrew culture | Statement: [Atbash, originCulture, ancient Hebrew culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originCulture Context triple: [Atbash, originCulture, ancient Hebrew culture]
-
A.
cultureOfOrigin
chosen
Indicates the cultural background or tradition from which an entity originates or is derived.
-
B.
originalNationality
Indicates the country or nationality an entity initially belonged to or originated from, before any later changes in citizenship or affiliation.
-
C.
originalHomeland
Indicates the place or region that is considered the ancestral or earliest homeland of an entity.
-
D.
originalLanguageCountry
Indicates the country where a work’s original language is primarily spoken or officially used.
-
E.
primaryCulture
Indicates the main or dominant culture associated with an entity, typically in contrast to any secondary or additional cultures.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.