Triple
T35308293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Hadi ila’l-Haqq Yahya |
E1019696
|
entity |
| Predicate | aimOfRule |
P181560
|
FINISHED |
| Object | unify northern Yemen under Zaydi imamate |
—
|
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: unify northern Yemen under Zaydi imamate | Statement: [al-Hadi ila’l-Haqq Yahya, aimOfRule, unify northern Yemen under Zaydi imamate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfRule Context triple: [al-Hadi ila’l-Haqq Yahya, aimOfRule, unify northern Yemen under Zaydi imamate]
-
A.
goalOfRule
chosen
Indicates that something is the intended objective or outcome that a particular rule is designed to achieve.
-
B.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
subjectOfRule
Indicates that an entity is governed, constrained, or described by a particular rule.
-
D.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
-
E.
basisOfRule
Indicates that something serves as the foundational principle, source, or justification upon which a rule is established or derived.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79052ed048190afc63b2c29b9758b |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.