Triple
T7680419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ständerat |
E173976
|
entity |
| Predicate | representsPrinciple |
P78892
|
FINISHED |
| Object | federalism in Switzerland |
—
|
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: federalism in Switzerland | Statement: [Ständerat, representsPrinciple, federalism in Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsPrinciple Context triple: [Ständerat, representsPrinciple, federalism in Switzerland]
-
A.
recognizesPrinciple
Indicates that an entity acknowledges the validity, authority, or applicability of a particular principle.
-
B.
implementsPrinciple
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
C.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
D.
invokesPrinciple
Indicates that one entity calls upon, applies, or relies on a particular principle as the basis for an action, decision, or reasoning process.
-
E.
includePrinciple
Indicates that one entity incorporates, embodies, or is based on a particular principle defined by another entity.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7048a01508190bc2e9ae8b863486c |
completed | March 27, 2026, 10:28 p.m. |
Created at: March 27, 2026, 4:01 p.m.