Triple
T13496505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Décret n° 2014-168 du 17 février 2014 |
E320774
|
entity |
| Predicate | numéroOfficiel |
P8195
|
FINISHED |
| Object | 2014-168 |
—
|
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: 2014-168 | Statement: [Décret n° 2014-168 du 17 février 2014, numéroOfficiel, 2014-168]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numéroOfficiel Context triple: [Décret n° 2014-168 du 17 février 2014, numéroOfficiel, 2014-168]
-
A.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
-
B.
corpsNumber
Indicates that an entity is assigned a specific corps identification number within an organized group or military structure.
-
C.
number
chosen
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
D.
symbolNumber
Indicates a relationship where a specific numerical identifier is assigned to or associated with a particular symbol.
-
E.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
- 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.