Triple
T7001497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmo svizzero |
E162346
|
entity |
| Predicate | uso |
P73516
|
FINISHED |
| Object | inno nazionale ufficiale della 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: inno nazionale ufficiale della Svizzera | Statement: [Salmo svizzero, uso, inno nazionale ufficiale della Svizzera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uso Context triple: [Salmo svizzero, uso, inno nazionale ufficiale della Svizzera]
-
A.
to
Indicates a directional or goal-oriented relationship in which something is directed, transferred, or oriented toward a target or endpoint.
-
B.
in
Indicates that one entity is located within the spatial, temporal, or conceptual bounds of another entity.
-
C.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
D.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
E.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c6d8c575f081908b43d95d1d99b1a4 |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.