Triple
T35774625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griva |
E1034256
|
entity |
| Predicate | formerlySeparateSettlement |
P5557
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Griva, formerlySeparateSettlement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlySeparateSettlement Context triple: [Griva, formerlySeparateSettlement, yes]
-
A.
hasFormerSettlement
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
-
B.
formerMunicipalityOf
chosen
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
C.
formerMainSettlement
Indicates that a location was previously the primary or most important settlement of a given area, but no longer holds that status.
-
D.
wasDividedFrom
Indicates that one entity was separated or split off from another entity, resulting in two distinct parts or groups.
-
E.
landsPreviouslyBelongedTo
Indicates that the specified lands were owned, controlled, or possessed by a different party at an earlier time.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: May 3, 2026, 4:06 p.m.