Triple
T29909759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retirement of Emperor Charles V |
E759646
|
entity |
| Predicate | placeOfSeclusion |
P63623
|
FINISHED |
| Object | Monastery of Yuste |
—
|
NE NERFINISHED |
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: Monastery of Yuste | Statement: [Retirement of Emperor Charles V, placeOfSeclusion, Monastery of Yuste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfSeclusion Context triple: [Retirement of Emperor Charles V, placeOfSeclusion, Monastery of Yuste]
-
A.
hidingPlace
Indicates a location or object that serves as a concealed or secret place where something or someone is hidden.
-
B.
undergroundConfinementLocation
Indicates that an entity is confined or held in a location that is physically underground.
-
C.
placeOfRetreat
chosen
Indicates a relationship where a location serves as a refuge or retreat for an entity, typically used for rest, seclusion, or recovery.
-
D.
sunkPlace
Indicates that one entity caused another (typically a vessel or structure) to sink at a specific location.
-
E.
hasSeclusion
Indicates that one entity provides, involves, or is characterized by a state or condition of privacy, isolation, or separation from others for another entity.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 6:09 p.m.