Triple
T28689786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Gayane Church |
E729244
|
entity |
| Predicate | bellTowerAddedIn |
P165219
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Saint Gayane Church, bellTowerAddedIn, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bellTowerAddedIn Context triple: [Saint Gayane Church, bellTowerAddedIn, 17th century]
-
A.
bellTowerCompletionDate
Indicates the date on which a bell tower was completed or finished being constructed.
-
B.
clockTowerAdded
Indicates that a clock tower has been newly constructed or incorporated into an existing structure or location.
-
C.
bellTowerStyle
Indicates the architectural style or design type of a bell tower in relation to a building or structure.
-
D.
bellTowerConstructionStart
Indicates the time or event at which the construction of a bell tower begins.
-
E.
hasBellTower
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 5:35 a.m.