Triple
T37836674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ლევან კობიაშვილი |
E943355
|
entity |
| Predicate | ნაკრებში_ამხანაგური_და_სOfficialuri |
P189546
|
FINISHED |
| Object | 100-ზე მეტი მატჩი |
—
|
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: 100-ზე მეტი მატჩი | Statement: [ლევან კობიაშვილი, ნაკრებში_ამხანაგური_და_სOfficialuri, 100-ზე მეტი მატჩი]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ნაკრებში_ამხანაგური_და_სOfficialuri Context triple: [ლევან კობიაშვილი, ნაკრებში_ამხანაგური_და_სOfficialuri, 100-ზე მეტი მატჩი]
-
A.
areOfficialIn
Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
-
B.
აქვს შენაკადი
Indicates that one watercourse serves as a tributary flowing into another watercourse.
-
C.
officialNameInArmenian
Indicates the officially recognized name of an entity as expressed in the Armenian language.
-
D.
includesOfficials
Indicates that one entity contains or encompasses certain officials as part of its composition or scope.
-
E.
nobleAssembly
Indicates that an entity participates in or is associated with a formal gathering or council of nobles.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.