Triple
T33011149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Ljeviš |
E844646
|
entity |
| Predicate | conversionToMosqueCentury |
P69501
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Our Lady of Ljeviš, conversionToMosqueCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionToMosqueCentury Context triple: [Our Lady of Ljeviš, conversionToMosqueCentury, 16th century]
-
A.
convertedToMosqueInCentury
chosen
Indicates that a building or religious structure was converted into a mosque during a specified century.
-
B.
convertedToMosque
Indicates that a building or structure was changed in function or use to become a mosque.
-
C.
reconvertedToMosqueBy
Indicates that a building or site, previously used for another purpose, was changed back into a mosque by a specific agent or authority.
-
D.
conversionToChristianityCentury
Indicates the century during which an entity underwent or was associated with a conversion to Christianity.
-
E.
usePeriodAsMosque
Indicates that a particular time period is utilized or designated for functioning as a mosque or for mosque-related activities.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:23 a.m.