Triple
T1344697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rembrandt’s “Danaë” |
E28543
|
entity |
| Predicate | significantModificationDate |
P24446
|
FINISHED |
| Object | circa 1643 |
—
|
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: circa 1643 | Statement: [Rembrandt’s “Danaë”, significantModificationDate, circa 1643]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantModificationDate Context triple: [Rembrandt’s “Danaë”, significantModificationDate, circa 1643]
-
A.
modificationDate
Indicates the date and time at which an entity was last changed or updated.
-
B.
majorRevisionDate
chosen
Indicates the date on which an entity underwent a significant or substantial update or revision.
-
C.
lastCreationDate
Indicates the most recent date and time at which the entity was created or newly instantiated.
-
D.
significantRevisionIn
Indicates that one entity represents a substantial or important change made within another entity, such as a major update or revision occurring in a larger work or version.
-
E.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23d696c8190bb688274280cb680 |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.