Triple
T3643201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monastery of Santa Clara-a-Velha |
E77236
|
entity |
| Predicate | dateOfAbandonment |
P49984
|
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: [Monastery of Santa Clara-a-Velha, dateOfAbandonment, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfAbandonment Context triple: [Monastery of Santa Clara-a-Velha, dateOfAbandonment, 17th century]
-
A.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
B.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
C.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
D.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
E.
dateAbolished
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc35acf2c81908f60168e93b773b1 |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:24 p.m.