Triple
T24876875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Carthusian Monastery of Valldemossa |
E622593
|
entity |
| Predicate | residencePeriod |
P157430
|
FINISHED |
| Object | winter 1838–1839 |
—
|
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: winter 1838–1839 | Statement: [Royal Carthusian Monastery of Valldemossa, residencePeriod, winter 1838–1839]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residencePeriod Context triple: [Royal Carthusian Monastery of Valldemossa, residencePeriod, winter 1838–1839]
-
A.
mainResidencePeriod
Indicates the time span during which a particular place serves as an entity’s primary or main residence.
-
B.
residencyDuration
Indicates the length of time an entity has continuously resided or stayed in a particular place or jurisdiction.
-
C.
timePeriodLivedIn
Indicates the time span or historical period during which an entity existed or was alive.
-
D.
periodOfResidenceStart
Indicates the date or point in time when an entity’s period of residence at a particular place begins.
-
E.
yearOfPermanentResidency
Indicates the specific year in which an entity began or was granted permanent residency in a particular place.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:24 a.m.