Triple
T9035261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hethum I of Armenia |
E216474
|
entity |
| Predicate | aimOfAlliance |
P85800
|
FINISHED |
| Object | to secure protection for Cilician Armenia |
—
|
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: to secure protection for Cilician Armenia | Statement: [Hethum I of Armenia, aimOfAlliance, to secure protection for Cilician Armenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfAlliance Context triple: [Hethum I of Armenia, aimOfAlliance, to secure protection for Cilician Armenia]
-
A.
aimOfAllies
Indicates that one entity represents the shared goal or objective pursued collectively by a group of allied entities.
-
B.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
C.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
D.
allianceScope
Indicates the extent or boundaries of cooperation and mutual obligations defined within an alliance relationship.
-
E.
allianceDesignation
Indicates a formal relationship in which one entity designates or classifies another as an ally within an alliance.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6abf4af481908d21245332329d99 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.