Triple
T18872677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EEA Agreement signed in 1992 |
E461609
|
entity |
| Predicate | statusOfSwitzerland |
P133284
|
FINISHED |
| Object | signed but not ratified |
—
|
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: signed but not ratified | Statement: [EEA Agreement signed in 1992, statusOfSwitzerland, signed but not ratified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfSwitzerland Context triple: [EEA Agreement signed in 1992, statusOfSwitzerland, signed but not ratified]
-
A.
economicRankInSwitzerland
Indicates the relative economic standing or rank of an entity within the context of Switzerland’s economy.
-
B.
governingCantonCapital
Indicates that a city serves as the capital and administrative seat of the specified canton.
-
C.
operatesInCanton
Indicates that an entity conducts its activities or has operational presence within a specified canton.
-
D.
joinedSwitzerland
Indicates that an entity became a member of, or was formally incorporated into, Switzerland.
-
E.
certificationSwitzerland
Indicates that an entity holds or is associated with a certification that is valid, issued, or recognized in Switzerland.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2aa9074819092137d236df3717b |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.