Triple
T15586262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamia II Gurieli |
E374628
|
entity |
| Predicate | regionRuledLocatedIn |
P119313
|
FINISHED |
| Object | western Georgia |
—
|
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: western Georgia | Statement: [Mamia II Gurieli, regionRuledLocatedIn, western Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionRuledLocatedIn Context triple: [Mamia II Gurieli, regionRuledLocatedIn, western Georgia]
-
A.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
B.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
C.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
D.
regionSeatLocatedIn
Indicates that the administrative seat or capital of a region is located within that region.
-
E.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e4900408190aadb48b001db4169 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:11 a.m.