Triple
T16186451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zelenograd |
E392816
|
entity |
| Predicate | hasAdministrativeOkrugStatusSince |
P40610
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Zelenograd, hasAdministrativeOkrugStatusSince, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeOkrugStatusSince Context triple: [Zelenograd, hasAdministrativeOkrugStatusSince, 1991]
-
A.
hasAdministrativeStatusSince
chosen
Indicates that an entity has held a particular administrative status continuously from a specified point in time onward.
-
B.
hasVoivodeshipStatusInPast
Indicates that an entity previously held the status of a voivodeship (administrative region) but no longer does so.
-
C.
hasLocalGovernmentStatusSinceCountryFormation
Indicates that an entity has held local government status continuously since the time its country was formed.
-
D.
hasMunicipalStatusUntil
Indicates that an entity possessed municipal status up to, but not beyond, a specified point in time.
-
E.
hasCountyAdministrativeBoard
Indicates that an entity is under the jurisdiction or responsibility of a specific county administrative board.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22061f47481909ededd5eed40f5a4 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.