Triple
T33049524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Athens |
E845685
|
entity |
| Predicate | reformEffectiveYear |
P23631
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [South Athens, reformEffectiveYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformEffectiveYear Context triple: [South Athens, reformEffectiveYear, 2011]
-
A.
effectiveYear
chosen
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
B.
repealEffectiveIn
Indicates that a repeal of a law, rule, or regulation becomes legally operative within a specified jurisdiction or context.
-
C.
reformDate
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
D.
repealEffectiveForNewPeriod
Indicates that a previously repealed rule or provision becomes effective again for a newly defined time period.
-
E.
constitutionEffectiveFrom
Indicates the date or point in time from which a particular constitution or constitutional provision is legally in force and applicable.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.