Triple
T3011709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | მტკვარი |
E82235
|
entity |
| Predicate | ქვემო_ნაკადის_ტიპი |
P3833
|
FINISHED |
| Object | დელტას მსგავსი შესართავი კასპიის ზღვაში |
—
|
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: დელტას მსგავსი შესართავი კასპიის ზღვაში | Statement: [მტკვარი, ქვემო_ნაკადის_ტიპი, დელტას მსგავსი შესართავი კასპიის ზღვაში]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ქვემო_ნაკადის_ტიპი Context triple: [მტკვარი, ქვემო_ნაკადის_ტიპი, დელტას მსგავსი შესართავი კასპიის ზღვაში]
-
A.
drainageType
chosen
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
B.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
C.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an entity.
-
D.
valleyType
Indicates the specific kind or classification of a valley that characterizes the relationship between the entities.
-
E.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a66c334819082d1d320c48eca1b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.