Triple
T112692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yiddish |
E2281
|
entity |
| Predicate | experiencedDeclineDuring |
P2924
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Yiddish, experiencedDeclineDuring, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedDeclineDuring Context triple: [Yiddish, experiencedDeclineDuring, 20th century]
-
A.
declineBeganInDecade
Indicates that the period of decline for an entity or phenomenon started during the specified decade.
-
B.
declinedDuring
chosen
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
collapsedDuring
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
-
E.
retrocededTo
Indicates that control, ownership, or rights over something were returned or transferred back from one entity to another.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.