Triple
T30516944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afrin region (historical) |
E776591
|
entity |
| Predicate | autonomyPeriodStart |
P169808
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Afrin region (historical), autonomyPeriodStart, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomyPeriodStart Context triple: [Afrin region (historical), autonomyPeriodStart, 2012]
-
A.
autonomyPeriod
Indicates the length of time during which an entity operates independently or without external control or intervention.
-
B.
reauthorizationPeriodStart
Indicates the point in time when a new or renewed authorization period begins.
-
C.
grantPeriodStart
Indicates the date or time at which a grant’s active period or coverage begins.
-
D.
hadAutonomyUntil
Indicates that an entity possessed a certain degree of self-governance or independent decision-making authority up to a specific point in time, after which that autonomy ceased or was reduced.
-
E.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68806f4888190a09e1753397c13ba |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:16 p.m.