Triple
T5169344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordonnance sur la procédure criminelle |
E116636
|
entity |
| Predicate | enactedInCentury |
P10303
|
FINISHED |
| Object | XVIIe siècle |
—
|
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: XVIIe siècle | Statement: [Ordonnance sur la procédure criminelle, enactedInCentury, XVIIe siècle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enactedInCentury Context triple: [Ordonnance sur la procédure criminelle, enactedInCentury, XVIIe siècle]
-
A.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
B.
foundedInCentury
Indicates that an entity was established or came into existence during a specified century.
-
C.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
-
D.
developedSinceCentury
Indicates that something began to be developed or came into existence starting from a specified century onward.
-
E.
century
chosen
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794dd9988190922e138f2a9a3c62 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.