Triple
T1899310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Dutch Mint |
E37655
|
entity |
| Predicate | previousLocationTime |
P32936
|
FINISHED |
| Object | Utrecht until 2020 |
—
|
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: Utrecht until 2020 | Statement: [Royal Dutch Mint, previousLocationTime, Utrecht until 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousLocationTime Context triple: [Royal Dutch Mint, previousLocationTime, Utrecht until 2020]
-
A.
currentLocationSince
Indicates the point in time since which an entity has been at its current location.
-
B.
visitedLocation
Indicates that an entity has gone to or spent time at a particular location.
-
C.
previousMeetingPlace
Indicates the location where two or more entities met on a prior occasion.
-
D.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
E.
tracksLocation
Indicates that one entity monitors and records the geographic position or movement of another entity over time.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb17181b0819090683c55fd1352cb |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb09b27e88190bff164040fef6d7e |
completed | March 7, 2026, 4:59 a.m. |
Created at: March 4, 2026, 7:35 p.m.