Triple
T7001500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmo svizzero |
E162346
|
entity |
| Predicate | funzione |
P68285
|
FINISHED |
| Object | esprimere identità nazionale svizzera |
—
|
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: esprimere identità nazionale svizzera | Statement: [Salmo svizzero, funzione, esprimere identità nazionale svizzera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funzione Context triple: [Salmo svizzero, funzione, esprimere identità nazionale svizzera]
-
A.
기능
chosen
Indicates that an entity has a particular function, role, or operational capability.
-
B.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
-
C.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
D.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
E.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0f8830819091f4356296234713 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.