Triple
T35788402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head of the Bahá'í Faith |
E1034622
|
entity |
| Predicate | leadershipModelAfter1957 |
P126736
|
FINISHED |
| Object | collective leadership |
—
|
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: collective leadership | Statement: [Head of the Bahá'í Faith, leadershipModelAfter1957, collective leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadershipModelAfter1957 Context triple: [Head of the Bahá'í Faith, leadershipModelAfter1957, collective leadership]
-
A.
leadershipEvolution
chosen
Indicates how leadership roles, styles, or structures change or develop over time within a given context.
-
B.
leadershipContext
Indicates the situational or organizational setting in which leadership is exercised or expressed between entities.
-
C.
hasTypeOfLeadership
Indicates that an entity possesses or is characterized by a specific style or form of leadership.
-
D.
hadLeadershipFrom
Indicates that one entity received leadership, guidance, or direction from another entity.
-
E.
leadershipImplication
Indicates that one entity’s leadership role, behavior, or position has consequences, influence, or inferred responsibilities for another entity or situation.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:06 p.m.