Triple
T2002568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BYN |
E43502
|
entity |
| Predicate | subdivisionUnit |
P28620
|
FINISHED |
| Object | kapeyka |
—
|
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: kapeyka | Statement: [BYN, subdivisionUnit, kapeyka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionUnit Context triple: [BYN, subdivisionUnit, kapeyka]
-
A.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
B.
subdivisionRank
Indicates the hierarchical level or type of administrative or territorial subdivision that an entity occupies within a larger organizational or geographic structure.
-
C.
subdivisionName1
Indicates that the first named subdivision is identified by a specific name or designation within a larger geographic or organizational hierarchy.
-
D.
subunitOf
chosen
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
E.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8820cec8190a945e5daeb8c9df6 |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.