Triple
T15251431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paço de São Cristóvão |
E364526
|
entity |
| Predicate | startDateAsRoyalResidence |
P117780
|
FINISHED |
| Object | 1808 |
—
|
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: 1808 | Statement: [Paço de São Cristóvão, startDateAsRoyalResidence, 1808]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateAsRoyalResidence Context triple: [Paço de São Cristóvão, startDateAsRoyalResidence, 1808]
-
A.
startDateAsPrincipalRoyalResidence
Indicates the date on which a location first began serving as the primary royal residence.
-
B.
startDateOfCurrentUseAsRoyalResidence
Indicates the date on which a place or building began its current period of use as a royal residence.
-
C.
endDateAsPrincipalRoyalResidence
Indicates the date on which a location ceased to serve as the primary royal residence.
-
D.
usedAsRoyalResidenceUntil
Indicates that something served as a royal residence up to a specified point in time.
-
E.
officialRoyalResidenceSince
Indicates that a location has served as the formal royal residence of a specified royal person or house starting from a given point in 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f728648190b2c86e4528542b65 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.