Triple
T20615965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurage |
E506566
|
entity |
| Predicate | subjectToProvincialLaw |
P120344
|
FINISHED |
| Object | Hainaut provincial regulations |
—
|
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: Hainaut provincial regulations | Statement: [Maurage, subjectToProvincialLaw, Hainaut provincial regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToProvincialLaw Context triple: [Maurage, subjectToProvincialLaw, Hainaut provincial regulations]
-
A.
isProvincial
Indicates that something belongs to, is characteristic of, or is administered at the level of a province rather than a national or local level.
-
B.
appliesLocalLaw
chosen
Indicates that a legal rule, decision, or authority is governed by and enforced under the laws of a specific local jurisdiction.
-
C.
stateLawAppliesFrom
Indicates that a particular state law becomes applicable starting from a specified point in time or under certain conditions.
-
D.
protectedProvince
Indicates that a province is under protection or safeguarding by another entity or authority.
-
E.
heldInProvince
Indicates that an event or activity takes place within the boundaries of a specified province.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aadbb3ac81908145f57fd6a94256 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.