Triple
T1499335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kandern region |
E29758
|
entity |
| Predicate | historicalTie |
P16345
|
FINISHED |
| Object | Swiss-German trade routes |
—
|
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: Swiss-German trade routes | Statement: [Kandern region, historicalTie, Swiss-German trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTie Context triple: [Kandern region, historicalTie, Swiss-German trade routes]
-
A.
hasHistoricalTieTo
Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
-
B.
historicallyLinked
chosen
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
C.
historicalOutcome
Indicates the result or consequence that an event, action, or situation produced in a historical context.
-
D.
historicallyContestedBy
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6f0ce988190aafab4a6e0dfd710 |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.