Triple
T28180848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antelias |
E716021
|
entity |
| Predicate | hasMonasteryOf |
P20652
|
FINISHED |
| Object | Armenian Catholicosate of the Great House of Cilicia |
—
|
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: Armenian Catholicosate of the Great House of Cilicia | Statement: [Antelias, hasMonasteryOf, Armenian Catholicosate of the Great House of Cilicia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasteryOf Context triple: [Antelias, hasMonasteryOf, Armenian Catholicosate of the Great House of Cilicia]
-
A.
hasMonasteryDedicatedTo
Indicates that a place or institution possesses a monastery whose religious dedication is to a specific figure, deity, or sacred concept.
-
B.
containsMonastery
chosen
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
C.
hasNearbyMonastery
Indicates that one entity is located close to or in the vicinity of a monastery.
-
D.
hasMonasteryRuins
Indicates that an entity possesses or contains the remains or ruins of a former monastery.
-
E.
hasNoResidentMonks
Indicates that a place or institution does not have any monks residing there.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 10:19 p.m.