Triple
T2105053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Democratic Front |
E37173
|
entity |
| Predicate | hadLeadershipFrom |
P35853
|
FINISHED |
| Object | church leaders |
—
|
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: church leaders | Statement: [United Democratic Front, hadLeadershipFrom, church leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadLeadershipFrom Context triple: [United Democratic Front, hadLeadershipFrom, church leaders]
-
A.
hasFormerLeader
Indicates that an entity previously held the role of leader of another entity but no longer does.
-
B.
notableFormerLeader
Indicates that the subject was once a leader of the object and is recognized as particularly significant or prominent in that former leadership role.
-
C.
adoptedByLeadersOf
Indicates that something has been formally accepted, endorsed, or implemented by the leaders of a specified group, organization, or community.
-
D.
mainLeaders
Indicates that the referenced entities serve as the primary or most important leaders within a group, organization, or context.
-
E.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbadcd4a081909d60b9b241950335 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb9ce3ff08190a9501f8bb821c01c |
completed | March 7, 2026, 5:38 a.m. |
Created at: March 4, 2026, 7:43 p.m.