Triple
T486523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concertgebouw |
E9890
|
entity |
| Predicate | royalDesignationYear |
P14035
|
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: [Concertgebouw, royalDesignationYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalDesignationYear Context triple: [Concertgebouw, royalDesignationYear, 2013]
-
A.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
B.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
C.
heirApparentDuringReign
Indicates that one entity was officially recognized as the designated heir apparent to another entity’s position or title during the latter’s period of reign.
-
D.
currentMonarchStart
Indicates the date or point in time when the current monarch’s reign began.
-
E.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bc6f548190b13dee42cb100423 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.