Triple
T21914422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerkhozhan |
E541145
|
entity |
| Predicate | usedAsToponymUntil |
P145617
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Gerkhozhan, usedAsToponymUntil, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsToponymUntil Context triple: [Gerkhozhan, usedAsToponymUntil, mid-20th century]
-
A.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
B.
usedAsToponymicBy
Indicates that one entity is employed as a place-based surname or name-forming element for another entity.
-
C.
usedAsCountyNameUntil
Indicates that an entity served as the official name of a county up to a specified point in time.
-
D.
usedAsTownNameFor
Indicates that something serves as the official or common name of a particular town.
-
E.
replacedByToponym
Indicates that one name or designation has been superseded and is now represented or referred to by a toponym (a place-based name).
- F. None of above. chosen
Provenance (4 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123366cb88190a42aa741e1245fd9 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 7:42 p.m.