Triple
T11017918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander First Class of the Order of the White Rose of Finland |
E260409
|
entity |
| Predicate | insigniaWornAt |
P55523
|
FINISHED |
| Object | neck |
—
|
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: neck | Statement: [Commander First Class of the Order of the White Rose of Finland, insigniaWornAt, neck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaWornAt Context triple: [Commander First Class of the Order of the White Rose of Finland, insigniaWornAt, neck]
-
A.
rankInsigniaWornOn
chosen
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
B.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
C.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
D.
insigniaUsedFor
Indicates that a particular insignia is employed or designated for a specific purpose, function, or use.
-
E.
insigniaName
Indicates the specific name or designation assigned to an insignia associated with an 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a7f4a881908232f99d18d95149 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.