Triple
T16597673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch police |
E403250
|
entity |
| Predicate | dateOfReorganization |
P44327
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Dutch police, dateOfReorganization, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfReorganization Context triple: [Dutch police, dateOfReorganization, 2013]
-
A.
reorganizationYear
chosen
Indicates the year in which an entity underwent a structural or organizational reorganization.
-
B.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
C.
furtherReorganizedOn
Indicates that an entity was reorganized again or to a greater extent on a specified later date or occasion.
-
D.
administrativeChangeDate
Indicates the date on which an administrative change (such as an update, modification, or reclassification) affecting the entity was officially recorded or took effect.
-
E.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d7367308190bf57b4a6a7bd33cc |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.