Triple
T22522937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argolis prefecture |
E556824
|
entity |
| Predicate | administrativeReformYear |
P44327
|
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: [Argolis prefecture, administrativeReformYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeReformYear Context triple: [Argolis prefecture, administrativeReformYear, 2011]
-
A.
timeOfMajorReforms
Indicates the specific time period during which significant reforms or major changes took place.
-
B.
yearOfGovernmentChange
Indicates the specific year in which a government was replaced, overthrown, or otherwise changed.
-
C.
reorganizationYear
chosen
Indicates the year in which an entity underwent a structural or organizational reorganization.
-
D.
lastReform
Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
-
E.
implementedReformsIn
Indicates that an entity (typically a person, organization, or government) carried out or put into effect specific reforms within a particular context, domain, or location.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e338dfc819082e1eeede3805fb9 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.