Triple
T2661532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Christians |
E54735
|
entity |
| Predicate | hadLeaders |
P1520
|
FINISHED |
| Object | apostles |
—
|
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: apostles | Statement: [Early Christians, hadLeaders, apostles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadLeaders Context triple: [Early Christians, hadLeaders, apostles]
-
A.
hadLeadershipFrom
Indicates that one entity received leadership, guidance, or direction from another entity.
-
B.
hasFormerLeader
Indicates that an entity previously held the role of leader of another entity but no longer does.
-
C.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
D.
mainLeaders
chosen
Indicates that the referenced entities serve as the primary or most important leaders within a group, organization, or context.
-
E.
hadExecutivePowerIn
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.