Triple
T24966916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rēzekne |
E624772
|
entity |
| Predicate | GORSis |
P157479
|
FINISHED |
| Object | Latgale Embassy |
—
|
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: Latgale Embassy | Statement: [Rēzekne, GORSis, Latgale Embassy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GORSis Context triple: [Rēzekne, GORSis, Latgale Embassy]
-
A.
ore
Indicates a relationship where a mineral-bearing rock or deposit contains a valuable metal or mineral in a form and concentration suitable for extraction.
-
B.
sojusznik
Indicates that one entity is an ally or supportive partner of another entity, typically cooperating toward shared goals or interests.
-
C.
isGSE
Indicates that one entity functions as a ground support equipment (GSE) resource used to support, service, or handle another entity, typically in an aerospace or aviation context.
-
D.
isGSE
Indicates that something is a Gene Set Enrichment (GSE) entity or is associated with a gene set enrichment analysis result.
-
E.
GSSP
Indicates a general social or situational participation relationship, where an entity is involved or takes part in a shared social, situational, or contextual setting with others.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6 a.m.