Triple
T25710473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabatieh Governorate |
E644714
|
entity |
| Predicate | hasEthnoReligiousGroup |
P62585
|
FINISHED |
| Object | Druze |
—
|
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: Druze | Statement: [Nabatieh Governorate, hasEthnoReligiousGroup, Druze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnoReligiousGroup Context triple: [Nabatieh Governorate, hasEthnoReligiousGroup, Druze]
-
A.
ethnicOrReligiousGroup
chosen
Indicates that one entity is an ethnic or religious group to which the other entity belongs or with which it is associated.
-
B.
hasEthnicGroupType
Indicates that an entity is associated with, characterized by, or classified according to a particular type or category of ethnic group.
-
C.
hasEthnoReligiousDimension
Indicates that the relationship, event, or phenomenon involves or is characterized by an ethnic and/or religious aspect or component.
-
D.
hasRecognizedEthnicGroup
Indicates that an entity includes or is associated with an ethnic group that is officially or socially recognized as distinct.
-
E.
ethnicRulingGroup
Indicates that a particular ethnic group holds primary political power or governing authority over a state or territory.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 9:11 p.m.