Triple
T28166469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | former Great Mosque of Málaga |
E715338
|
entity |
| Predicate | dedicatedToAfterConversion |
P164088
|
FINISHED |
| Object | Virgin Mary |
—
|
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: Virgin Mary | Statement: [former Great Mosque of Málaga, dedicatedToAfterConversion, Virgin Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedToAfterConversion Context triple: [former Great Mosque of Málaga, dedicatedToAfterConversion, Virgin Mary]
-
A.
hasConvertedTo
Indicates that an entity has changed its previous state, status, form, or affiliation into a new one.
-
B.
functionAfterConversion
Indicates that one function or behavior occurs as a result of, or is valid only after, a specified conversion has taken place.
-
C.
afterConversionKnownAs
Indicates that an entity is referred to by a new name or identifier after undergoing a conversion or transformation.
-
D.
someConvertedTo
Indicates that a portion of one entity has been transformed or changed into another entity.
-
E.
dedicatedToConcept
Indicates that something is specifically devoted, committed, or purposefully directed toward a particular concept or abstract idea.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64232c51c8190822b454b225e2af4 |
completed | May 2, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:10 p.m.