Triple
T21940106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eesti vapp |
E541793
|
entity |
| Predicate | funktsioon |
P81043
|
FINISHED |
| Object | riigi identiteedi tähis |
—
|
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: riigi identiteedi tähis | Statement: [Eesti vapp, funktsioon, riigi identiteedi tähis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funktsioon Context triple: [Eesti vapp, funktsioon, riigi identiteedi tähis]
-
A.
functie
chosen
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
B.
기능
Indicates that an entity has a particular function, role, or operational capability.
-
C.
formFunction
Indicates that one entity’s physical form, structure, or configuration determines or enables the function or role performed by another (or by itself).
-
D.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
E.
deFactoFunction
Indicates that one entity effectively serves or operates in the role or capacity of another entity, even if not formally or officially designated as such.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12420b1cc81909b375891aedc0979 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:55 p.m.