Triple
T22615742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | beylerbey |
E558139
|
entity |
| Predicate | declinedInImportanceAfter |
P32955
|
FINISHED |
| Object | 19th-century Tanzimat reforms |
—
|
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: 19th-century Tanzimat reforms | Statement: [beylerbey, declinedInImportanceAfter, 19th-century Tanzimat reforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declinedInImportanceAfter Context triple: [beylerbey, declinedInImportanceAfter, 19th-century Tanzimat reforms]
-
A.
lostImportanceUnder
chosen
Indicates that one entity’s importance or prominence decreased when another specified entity came into power, control, or influence.
-
B.
declineAfter
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
C.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
D.
declinedInPopularity
Indicates that something has become less popular or less favored over a period of time.
-
E.
declineBeganUnder
Indicates that a period of decline started during the tenure, rule, or administration of a specified entity.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167edec2481909c2f06607b3cb8f6 |
completed | April 29, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:59 p.m.