Triple
T19821127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanûn-ı Esâsî |
E476195
|
entity |
| Predicate | reactivatedOn |
P122863
|
FINISHED |
| Object | 1908 |
—
|
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: 1908 | Statement: [Kanûn-ı Esâsî, reactivatedOn, 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactivatedOn Context triple: [Kanûn-ı Esâsî, reactivatedOn, 1908]
-
A.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
B.
reactivatedFrom
Indicates that an entity has been brought back into an active state from a previously inactive, archived, or decommissioned state, often referencing the source state or version it was reactivated from.
-
C.
re-establishedOn
chosen
Indicates that a previously existing relationship, status, or entity was restored or brought back into effect on a specific date or time.
-
D.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified entity.
-
E.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fee3e48190ae728e49748ad268 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.