Triple
T3650253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yiddish literature |
E77401
|
entity |
| Predicate | incorporatesElementsFrom |
P50682
|
FINISHED |
| Object | Hebrew |
—
|
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: Hebrew | Statement: [Yiddish literature, incorporatesElementsFrom, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatesElementsFrom Context triple: [Yiddish literature, incorporatesElementsFrom, Hebrew]
-
A.
incorporatedRightsFrom
Indicates that one entity has absorbed, adopted, or integrated legal rights or entitlements that originally belonged to another entity.
-
B.
incorporatedAs
Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
-
C.
incorporatedThrough
Indicates that one entity was formed, established, or legally created by means of another specified process, mechanism, or intermediary entity.
-
D.
mergedInto
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
E.
incorporatedAgainst
Indicates that a legal entity was formally incorporated in opposition to, or as a countermeasure against, another party.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38fa1988190b630329700afc3dd |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adbae14d488190a6024548979c6faf |
completed | March 8, 2026, 6:07 p.m. |
Created at: March 8, 2026, 3:24 p.m.