Triple
T29303565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the Redeemer |
E743026
|
entity |
| Predicate | cityStateAtConstruction |
P47828
|
FINISHED |
| Object | Ani |
—
|
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: Ani | Statement: [Church of the Redeemer, cityStateAtConstruction, Ani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityStateAtConstruction Context triple: [Church of the Redeemer, cityStateAtConstruction, Ani]
-
A.
rulingStateAtConstruction
Indicates the political state or authority that held ruling control over a place or structure at the time it was originally constructed.
-
B.
countryDuringConstruction
Indicates the country in which something was located or took place during its construction period.
-
C.
constructionState
Indicates the current phase or status of progress in a construction or building process.
-
D.
cityDuringConstruction
chosen
Indicates that a city exists or is relevant during the time period in which a particular construction activity or project is taking place.
-
E.
governingCityState
Indicates that one city or state holds governing authority or administrative control over another specified region or entity.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a494248190b9262c99bea9c853 |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:11 p.m.