Triple
T27283565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mustafa Mughniyeh |
E688403
|
entity |
| Predicate | familyPoliticalAssociation |
P114381
|
FINISHED |
| Object | Hezbollah |
—
|
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: Hezbollah | Statement: [Mustafa Mughniyeh, familyPoliticalAssociation, Hezbollah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyPoliticalAssociation Context triple: [Mustafa Mughniyeh, familyPoliticalAssociation, Hezbollah]
-
A.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
-
B.
associatedPoliticalFamily
chosen
Indicates a relationship where an entity is linked or connected to a particular political family, dynasty, or lineage.
-
C.
familyAssociationWith
Indicates a familial relationship or connection exists between the referenced entities.
-
D.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 11:09 a.m.