Triple
T3137536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Dam |
E65568
|
entity |
| Predicate | royalPalaceConstructionPeriod |
P45593
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [De Dam, royalPalaceConstructionPeriod, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalPalaceConstructionPeriod Context triple: [De Dam, royalPalaceConstructionPeriod, 17th century]
-
A.
governingDynastyAtConstruction
Indicates the ruling dynasty that held power at the time a structure or monument was constructed.
-
B.
usedAsPresidentialPalaceSince
Indicates that something has served in the role of a presidential palace starting from a specified point in time.
-
C.
yearsInUseAsImperialPalace
Indicates the number of years a place served as the official imperial palace.
-
D.
usedAsRoyalResidenceUntil
Indicates that something served as a royal residence up to a specified point in time.
-
E.
dateOfMainRoyalMonument
Indicates the date on which a person's principal royal monument (such as a main tomb or commemorative structure) was established, completed, or formally dedicated.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada574509c81908a88bb10ea35516d |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:05 p.m.