Triple
T29616913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rickenbach |
E754886
|
entity |
| Predicate | hasRegionalLaw |
P196072
|
FINISHED |
| Object | Vorarlberg state law |
—
|
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: Vorarlberg state law | Statement: [Rickenbach, hasRegionalLaw, Vorarlberg state law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalLaw Context triple: [Rickenbach, hasRegionalLaw, Vorarlberg state law]
-
A.
hasProvincialLaw
chosen
Indicates that a jurisdiction or entity is governed by, or subject to, a specific provincial-level law.
-
B.
legalCodeAppliesTo
Indicates that a particular legal code or statute is applicable to, or governs, a specified subject, situation, or entity.
-
C.
existsInJurisdiction
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
-
D.
legalSystemRegion
Indicates the geographic or jurisdictional region within which a particular legal system is applicable or in force.
-
E.
legalLicenseJurisdiction
Indicates the legal authority or geographic area under whose laws a particular license is granted, valid, or enforced.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: April 28, 2026, 6:32 p.m.