Triple
T37785775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uplistsulis Eklesia |
E941951
|
entity |
| Predicate | countryHistoricRegion |
P915
|
FINISHED |
| Object | Kartli |
E15356
|
NE 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: Kartli | Statement: [Uplistsulis Eklesia, countryHistoricRegion, Kartli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryHistoricRegion Context triple: [Uplistsulis Eklesia, countryHistoricRegion, Kartli]
-
A.
historicalRegion
chosen
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
B.
historicallyImportantRegion
Indicates that a region holds significant importance due to its impact on historical events, developments, or cultural heritage.
-
C.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
D.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
-
E.
historicalCoreRegion
Indicates that a region served as the central or foundational area of a group, state, or civilization during a significant historical period.
- F. None of above.
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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f17f91a881909126471974b091dc |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.