Triple
T19270902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slavutych |
E481919
|
entity |
| Predicate | hasResidentialDistrict |
P9064
|
FINISHED |
| Object | Armenian quarter |
—
|
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: Armenian quarter | Statement: [Slavutych, hasResidentialDistrict, Armenian quarter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentialDistrict Context triple: [Slavutych, hasResidentialDistrict, Armenian quarter]
-
A.
hasResidentialArea
chosen
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
B.
hasResidentialBuildingsType
Indicates that an entity is associated with a specific type or category of residential buildings.
-
C.
isResidentialTown
Indicates that a town is primarily used or designated for residential living rather than for commercial, industrial, or other primary purposes.
-
D.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
E.
isResidentialUnitOf
Indicates that a specific residential unit (e.g., apartment, house) belongs to or is part of a larger property, building, or complex.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb8bea08190b5c65eebe67dccbb |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.