Triple
T33388774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DK0010272202 |
E854989
|
entity |
| Predicate | languageOfIssuerJurisdiction |
P34970
|
FINISHED |
| Object | Danish |
—
|
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: Danish | Statement: [DK0010272202, languageOfIssuerJurisdiction, Danish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfIssuerJurisdiction Context triple: [DK0010272202, languageOfIssuerJurisdiction, Danish]
-
A.
languageOfJurisdiction
chosen
Indicates the language officially used for legal and administrative purposes within a given jurisdiction.
-
B.
currencyOfJurisdiction
Indicates the official currency that is legally used within a particular jurisdiction or governing authority.
-
C.
languageOfIssue
Indicates the language in which a particular item, document, or resource is issued or published.
-
D.
countryOfJurisdiction
Indicates the country whose legal authority or jurisdiction governs or applies to a given entity, action, or arrangement.
-
E.
financialInstrumentJurisdiction
Indicates the jurisdiction or legal authority under which a financial instrument is issued, regulated, or legally governed.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: May 1, 2026, 1:35 a.m.