Triple
T30782568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGI |
E783856
|
entity |
| Predicate | systemStartEra |
P71816
|
FINISHED |
| Object | post-1999 Polish administrative division reform |
—
|
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: post-1999 Polish administrative division reform | Statement: [NGI, systemStartEra, post-1999 Polish administrative division reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemStartEra Context triple: [NGI, systemStartEra, post-1999 Polish administrative division reform]
-
A.
commandEra
Indicates the time period or era during which an entity held command or exercised authoritative control.
-
B.
originalRunEra
Indicates the time period or era during which something (such as a show, series, or product) was first originally run or released.
-
C.
marksNewEraFor
Indicates that one event, development, or change signifies the beginning of a distinct new period or phase for another.
-
D.
hasEraReset
chosen
Indicates that a new era or time period has been initiated, resetting the previous temporal sequence or counting.
-
E.
introductionEra
Indicates the historical period or era during which something was first introduced or came into use.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 29, 2026, 8:41 p.m.