Triple
T1828411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard of the President of Finland |
E40705
|
entity |
| Predicate | symbolCategory |
P13707
|
FINISHED |
| Object | state insignia of Finland |
—
|
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: state insignia of Finland | Statement: [Standard of the President of Finland, symbolCategory, state insignia of Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolCategory Context triple: [Standard of the President of Finland, symbolCategory, state insignia of Finland]
-
A.
symbolType
chosen
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
B.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
C.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
D.
labelCatalog
Indicates assigning or associating a descriptive label or identifier with a catalog entity or catalog entry.
-
E.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:32 p.m.