Triple
T36722899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recinte Modernista de Sant Pau |
E907115
|
entity |
| Predicate | functionedAsHospitalUntil |
P152019
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Recinte Modernista de Sant Pau, functionedAsHospitalUntil, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionedAsHospitalUntil Context triple: [Recinte Modernista de Sant Pau, functionedAsHospitalUntil, 2009]
-
A.
foundedAsHospital
Indicates that an organization was originally established as a hospital.
-
B.
medicalInstitutionUntil
chosen
Indicates that an entity functions as a medical institution for another entity or in a given context up to a specified end time or date.
-
C.
originalHospitalClosed
Indicates that the hospital where an event or treatment originally took place has since ceased operations or been shut down.
-
D.
hospitalEstablishedIn
Indicates that a hospital was founded, opened, or began operating in a specific year or time period.
-
E.
containsHospital
Indicates that one entity includes or encompasses a hospital within its boundaries or composition.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.