Triple
T8690878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Saint Gregory of Tigran Honents |
E206283
|
entity |
| Predicate | roofCondition |
P20761
|
FINISHED |
| Object | partially collapsed |
—
|
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: partially collapsed | Statement: [Church of Saint Gregory of Tigran Honents, roofCondition, partially collapsed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofCondition Context triple: [Church of Saint Gregory of Tigran Honents, roofCondition, partially collapsed]
-
A.
roofStatus
chosen
Indicates the current condition or state of a roof, such as whether it is intact, damaged, under repair, or replaced.
-
B.
buildingCondition
Indicates the physical state or quality of a building, such as how well it is preserved, maintained, or structurally sound.
-
C.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
D.
roofOptions
Indicates the available types or configurations of roofs that can be selected or applied to an entity.
-
E.
roofFunction
Indicates the functional role or purpose that a roof serves in relation to the structure it covers.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5735ffdc819094126e2698f98511 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.