Triple
T22086847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natanebi River |
E545799
|
entity |
| Predicate | isInPhysicalRegion |
P77476
|
FINISHED |
| Object | western part of 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 part of Georgia | Statement: [Natanebi River, isInPhysicalRegion, western part of Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPhysicalRegion Context triple: [Natanebi River, isInPhysicalRegion, western part of Georgia]
-
A.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
B.
isInSubregion
chosen
Indicates that one region or area is located within the boundaries of another, more specific subregion.
-
C.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
D.
isPortRegionOf
Indicates that a region functions as the port area associated with, or belonging to, a particular larger geographic or administrative entity.
-
E.
isInSameRegionAs
Indicates that two entities are located within the same defined geographic or administrative region.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e2e3108190883199f272756e4e |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.