Triple
T26390585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geschäftsführer |
E663398
|
entity |
| Predicate | isUsedInJurisdiction |
P16807
|
FINISHED |
| Object | Liechtenstein |
—
|
NE NERFINISHED |
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: Liechtenstein | Statement: [Geschäftsführer, isUsedInJurisdiction, Liechtenstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedInJurisdiction Context triple: [Geschäftsführer, isUsedInJurisdiction, Liechtenstein]
-
A.
usedForJurisdiction
Indicates that something (such as a rule, document, or authority) is applied to define, govern, or determine the scope of a particular jurisdiction.
-
B.
existsInJurisdiction
chosen
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
-
C.
hasJurisdictionalUse
Indicates that an entity has legal authority or recognized usage rights within a specific jurisdiction or territorial scope.
-
D.
jurisdictionUse
Indicates that one entity has the authority to apply, exercise, or enforce jurisdiction over the use or operation of another entity or resource.
-
E.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 11:25 p.m.