Triple
T369388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jøssingfjord |
E8234
|
entity |
| Predicate | usedAsSymbol |
P9907
|
FINISHED |
| Object | anti-Nazi sentiment in Norway |
—
|
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: anti-Nazi sentiment in Norway | Statement: [Jøssingfjord, usedAsSymbol, anti-Nazi sentiment in Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSymbol Context triple: [Jøssingfjord, usedAsSymbol, anti-Nazi sentiment in Norway]
-
A.
symbolicallyUses
chosen
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
usedInSignatureOf
Indicates that something (such as a type, parameter, or construct) appears as part of the formal signature of a function, method, or similar callable entity.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
usedBySystem
Indicates that something is utilized or operated by a particular system.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebfdb0608190b1794a871d0d237a |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.