Triple
T28451352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subotiv |
E716588
|
entity |
| Predicate | IllinskaChurchBuiltIn |
P36934
|
FINISHED |
| Object | 1653 |
—
|
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: 1653 | Statement: [Subotiv, IllinskaChurchBuiltIn, 1653]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IllinskaChurchBuiltIn Context triple: [Subotiv, IllinskaChurchBuiltIn, 1653]
-
A.
mainChurchBuilt
Indicates that the primary church associated with an entity was constructed or established at a particular time or by a particular agent.
-
B.
originalChurchBuilt
Indicates that a particular church building was initially constructed at a given time or by a specified agent, before any later reconstructions or modifications.
-
C.
isHistoricChurchIn
Indicates that a church, recognized as historic, is located within a specified geographic area or jurisdiction.
-
D.
foundingLocationOfChurch
Indicates the place where a particular church was originally founded or established.
-
E.
churchConstructionDate
chosen
Indicates the date on which a church was constructed or originally built.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e72b5208190869d49fcb3f0a546 |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:52 a.m.