Triple
T18365168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinfelden (Aargau) |
E440023
|
entity |
| Predicate | joinedCantonYear |
P70048
|
FINISHED |
| Object | 1803 |
—
|
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: 1803 | Statement: [Rheinfelden (Aargau), joinedCantonYear, 1803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedCantonYear Context triple: [Rheinfelden (Aargau), joinedCantonYear, 1803]
-
A.
establishedAsCanton
chosen
Indicates that an entity was formally created or designated as a canton within an administrative or political system.
-
B.
unionInCanton
Indicates that a trade union is located within, operates in, or is jurisdictionally associated with a specific canton.
-
C.
joinedSwitzerland
Indicates that an entity became a member of, or was formally incorporated into, Switzerland.
-
D.
joinedInYear
Indicates that an entity became a member of, or started participating in, another entity (such as an organization, group, or institution) in a specified calendar year.
-
E.
joinedAustriaInYear
Indicates that an entity became part of, or entered into union with, Austria in the specified year.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5174d31608190851a5bab6878c203 |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:38 a.m.