Triple
T37788028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | მიხეილ მესხის სახელობის სტადიონი |
E942008
|
entity |
| Predicate | ძირითადი დანიშნულება |
P78649
|
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.
primaryIntent
chosen
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
-
B.
primarySignificance
Indicates that something has the greatest importance, relevance, or impact among a set of related things or factors.
-
C.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
D.
centralGoal
Indicates that something is the primary objective or main aim around which other actions, plans, or considerations are organized.
-
E.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.