Triple
T10220336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appingedam |
E242557
|
entity |
| Predicate | administrativeChangeDate |
P92815
|
FINISHED |
| Object | 1 January 2021 |
—
|
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: 1 January 2021 | Statement: [Appingedam, administrativeChangeDate, 1 January 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeChangeDate Context triple: [Appingedam, administrativeChangeDate, 1 January 2021]
-
A.
amendedAt
Indicates the date and time at which an existing entity or record was modified or updated.
-
B.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
-
C.
changedOn
Indicates that an entity underwent a modification or update at a specific point in time.
-
D.
dateChangesWith
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
-
E.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa72b258819097d8d50a714e19dc |
completed | April 6, 2026, 12:43 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_69d3aa208c248190a0fb186b106389f3 |
completed | April 6, 2026, 12:42 p.m. |
Created at: April 6, 2026, 11:09 a.m.