Triple
T22497958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St. Mary of the Mongols |
E556193
|
entity |
| Predicate | continuouslyUsedAs |
P148441
|
FINISHED |
| Object | Orthodox church |
—
|
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: Orthodox church | Statement: [Church of St. Mary of the Mongols, continuouslyUsedAs, Orthodox church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuouslyUsedAs Context triple: [Church of St. Mary of the Mongols, continuouslyUsedAs, Orthodox church]
-
A.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
B.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
C.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb31b8081909553fa860a07e746 |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:50 p.m.