Triple
T2243973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | León |
E49458
|
entity |
| Predicate | conventoDeSanMarcosFunction |
P36432
|
FINISHED |
| Object | former monastery |
—
|
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: former monastery | Statement: [León, conventoDeSanMarcosFunction, former monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conventoDeSanMarcosFunction Context triple: [León, conventoDeSanMarcosFunction, former monastery]
-
A.
otherMajorBasilica
Indicates that one basilica stands in a specified relationship as an “other” major basilica to another, distinguishing it from a primary or reference major basilica.
-
B.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
C.
resultForMonument
Indicates that something (such as data, analysis, or an outcome) is the result specifically associated with a given monument.
-
D.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
E.
containsMonastery
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0c157e88190a5bc876d9591a24b |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.