Triple
T13496513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Décret n° 2014-168 du 17 février 2014 |
E320774
|
entity |
| Predicate | typeDeNorme |
P2826
|
FINISHED |
| Object | acte réglementaire |
—
|
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: acte réglementaire | Statement: [Décret n° 2014-168 du 17 février 2014, typeDeNorme, acte réglementaire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeDeNorme Context triple: [Décret n° 2014-168 du 17 février 2014, typeDeNorme, acte réglementaire]
-
A.
normType
chosen
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
B.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
C.
standardsType
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
-
D.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
E.
legalStandardType
Indicates the specific type or category of legal standard that governs or applies to a given legal rule, decision, or evaluation.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4e9ca4819083116890a65389f9 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.