Triple
T951854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aosta Valley |
E20538
|
entity |
| Predicate | hasSpecialStatute |
P21621
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aosta Valley, hasSpecialStatute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialStatute Context triple: [Aosta Valley, hasSpecialStatute, true]
-
A.
establishedByStatute
Indicates that something has been formally created, defined, or authorized through a specific law or statute.
-
B.
statuteInvolved
Indicates that a particular statute or legal provision is implicated, referenced, or applied in relation to a given case, event, or legal matter.
-
C.
hasLocalOrdinances
Indicates that a governing body or jurisdiction has established and enacted specific local ordinances or regulations.
-
D.
statuteInterpreted
Indicates that a legal authority (such as a court or agency) has provided an interpretation or authoritative reading of a particular statute.
-
E.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
- F. None of above. chosen
Provenance (4 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d757d08190a475cf47febd05ae |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b30efd2c8190b780a6dee086d0aa |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:40 p.m.