Triple
T28180974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholicos of the Great House of Cilicia |
E716024
|
entity |
| Predicate | parallelSeeTo |
P164657
|
FINISHED |
| Object | Catholicos of All Armenians |
—
|
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: Catholicos of All Armenians | Statement: [Catholicos of the Great House of Cilicia, parallelSeeTo, Catholicos of All Armenians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelSeeTo Context triple: [Catholicos of the Great House of Cilicia, parallelSeeTo, Catholicos of All Armenians]
-
A.
parallel
Indicates that two or more entities maintain a constant separation and direction without intersecting or converging.
-
B.
parallelPosition
Indicates that two entities occupy positions that are aligned in parallel relative to a reference frame or axis.
-
C.
parallelType
Indicates that one entity runs in parallel to another, specifying the type or manner of their parallel relationship.
-
D.
parallelService
Indicates that two or more services operate concurrently or in parallel rather than sequentially.
-
E.
parallelEvent
Indicates that two or more events occur at the same time or overlap in time without a required order between them.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 27, 2026, 10:19 p.m.