Triple
T3218575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosque of Cristo de la Luz |
E67454
|
entity |
| Predicate | convertedToChurch |
P46584
|
FINISHED |
| Object | 12th 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: 12th century | Statement: [Mosque of Cristo de la Luz, convertedToChurch, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToChurch Context triple: [Mosque of Cristo de la Luz, convertedToChurch, 12th century]
-
A.
convertedToTemple
Indicates that something has been transformed, repurposed, or officially designated to function as a temple.
-
B.
convertedToTempleAfter
Indicates that a structure or place was transformed from its original use into a temple at a later time.
-
C.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
D.
convertedFor
Indicates that one entity has been transformed, adapted, or reformatted specifically for use, compatibility, or suitability with another entity.
-
E.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab0c48b481909d1bd9dc41dfa8c2 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:08 p.m.