Triple
T963669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Büsingen am Hochrhein |
E20788
|
entity |
| Predicate | hasSpecialTaxArrangements |
P21912
|
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, hasSpecialTaxArrangements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialTaxArrangements Context triple: [Büsingen am Hochrhein, hasSpecialTaxArrangements, 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.
typeOfTaxpayerCovered
Indicates the category or kind of taxpayer to which a particular rule, obligation, or provision applies.
-
C.
customsRegime
Indicates the specific customs treatment or regulatory framework under which goods are imported, exported, or stored.
-
D.
hasFreeTradeAgreement
Indicates that two entities are linked by a formal free trade agreement that reduces or eliminates trade barriers between them.
-
E.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b416cf4c8190bd685227db25fb53 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.