Triple
T28348481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalny |
E718021
|
entity |
| Predicate | presentAdministrativeStatus |
P38445
|
FINISHED |
| Object | sub-provincial city |
—
|
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: sub-provincial city | Statement: [Dalny, presentAdministrativeStatus, sub-provincial city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentAdministrativeStatus Context triple: [Dalny, presentAdministrativeStatus, sub-provincial city]
-
A.
administrativeStatusCurrent
chosen
Indicates the current administrative status or condition of an entity within a governing or managing system.
-
B.
administrativeStatusOfEntityRepresented
Indicates the current administrative or operational status assigned to the entity that is being represented.
-
C.
formerAdministrativeStatus
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
D.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
E.
hasCurrentAdministrativeEntity
Indicates that an entity is currently governed, managed, or overseen by a specific administrative body or authority.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 12:44 a.m.