Triple
T23336208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Зея |
E591591
|
entity |
| Predicate | код в ГВР России |
P775
|
FINISHED |
| Object | 20010100112117500000000 (приблизительно, может отличаться в деталях) |
—
|
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: 20010100112117500000000 (приблизительно, может отличаться в деталях) | Statement: [Зея, код в ГВР России, 20010100112117500000000 (приблизительно, может отличаться в деталях)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: код в ГВР России Context triple: [Зея, код в ГВР России, 20010100112117500000000 (приблизительно, может отличаться в деталях)]
-
A.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
B.
codifiedIn
chosen
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
C.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
D.
engineCode
Indicates a relationship where an entity is associated with a specific engine identification code or designation.
-
E.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197f1e0588190bf073b92be0bf9e4 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:16 p.m.