Triple
T1261698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Büsingen am Hochrhein customs enclave context |
E12515
|
entity |
| Predicate | usesSwissVATSystem |
P23810
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Büsingen am Hochrhein customs enclave context, usesSwissVATSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSwissVATSystem Context triple: [Büsingen am Hochrhein customs enclave context, usesSwissVATSystem, true]
-
A.
hasCustomsUnion
Indicates that two or more entities participate in a customs union, sharing a common external tariff and removing customs duties between them.
-
B.
hasCanton
Indicates that an entity is administratively divided into, or associated with, a specific canton.
-
C.
hasMemberInEEA
Indicates that an entity has at least one member who is located in, based in, or belongs to the European Economic Area (EEA).
-
D.
usesExchangeRateRegime
Indicates that one entity adopts or operates under a particular exchange rate regime in conducting its currency or monetary arrangements.
-
E.
taxationMethod
chosen
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc64e648190b9c4f980eb8168aa |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.