Triple
T17080842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Safe Confinement |
E414463
|
entity |
| Predicate | slidIntoPositionDate |
P125805
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [New Safe Confinement, slidIntoPositionDate, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slidIntoPositionDate Context triple: [New Safe Confinement, slidIntoPositionDate, 2016]
-
A.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
B.
entryDate
Indicates the date on which an entity was first recorded, created, or entered into a system or context.
-
C.
occupationDate
Indicates the date or time period during which an entity assumes, holds, or begins a particular role, position, or occupation.
-
D.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
-
E.
laidDownDate
Indicates the date on which something (such as a rule, law, standard, or foundation) was formally established, set, or put in place.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe2fe7c819099ab0586b1a119f6 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.