Triple
T5560283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaverdi Monastery |
E145747
|
entity |
| Predicate | heightClaim |
P64481
|
FINISHED |
| Object | one of the tallest medieval churches in Georgia |
—
|
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: one of the tallest medieval churches in Georgia | Statement: [Alaverdi Monastery, heightClaim, one of the tallest medieval churches in Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightClaim Context triple: [Alaverdi Monastery, heightClaim, one of the tallest medieval churches in Georgia]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
C.
heightRestriction
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
D.
heightInInches
Indicates that one entity has a specific height measured in inches.
-
E.
heightEstimate
Indicates an estimated or approximate value for the height of an entity, rather than a precisely measured height.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201857848190a5443b51bcdb63fa |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:36 p.m.