Triple
T13045041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armiansk urban hromada |
E327295
|
entity |
| Predicate | hasCentralSettlementStatus |
P58138
|
FINISHED |
| Object | town |
—
|
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: town | Statement: [Armiansk urban hromada, hasCentralSettlementStatus, town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralSettlementStatus Context triple: [Armiansk urban hromada, hasCentralSettlementStatus, town]
-
A.
hasCenterStatus
chosen
Indicates that an entity holds a designated central role, position, or status within a system, organization, or structure.
-
B.
hasCentralClaim
Indicates that one entity presents or embodies the main assertion, thesis, or primary point made by another entity.
-
C.
settlementState
Indicates the state or status of a settlement process or transaction at a given point in time.
-
D.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
E.
isRemoteSettlement
Indicates that a settlement is located in a remote, sparsely connected, or isolated area relative to major population centers or infrastructure.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:56 p.m.