Triple
T19197319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landtag of Salzburg |
E470004
|
entity |
| Predicate | appliesLawArea |
P2167
|
FINISHED |
| Object | state law of Salzburg |
—
|
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: state law of Salzburg | Statement: [Landtag of Salzburg, appliesLawArea, state law of Salzburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesLawArea Context triple: [Landtag of Salzburg, appliesLawArea, state law of Salzburg]
-
A.
legalArea
chosen
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
-
B.
appliedLawFrom
Indicates that a specific law or legal provision was applied or derived from a particular source, context, or jurisdiction in a legal decision or situation.
-
C.
appliesLawThrough
Indicates that one entity enforces, implements, or carries out a law or legal rule by means of another entity or mechanism.
-
D.
notableAreaOfLaw
Indicates that a person or entity is particularly recognized or distinguished in a specific field or area of law.
-
E.
appliesToFieldOfLaw
Indicates that something is relevant or applicable to a particular field or branch of law.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a695cc8190b84a220f52c51dfc |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.