Triple
T37788026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | მიხეილ მესხის სახელობის სტადიონი |
E942008
|
entity |
| Predicate | სახელწოდება |
P744
|
FINISHED |
| Object | მიხეილ მესხის სახელობის სტადიონი |
—
|
NE NERFINISHED |
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.
nameOf
chosen
Indicates that one entity is the name or designation of another entity.
-
B.
displayName
Indicates the human-readable name or label that is shown to users when presenting an entity.
-
C.
namesakeDescription
Indicates that the object provides a descriptive explanation of why or how the subject is considered a namesake of something or someone.
-
D.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
E.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.