Triple
T37887848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Brotherhood (Invisible Man) |
E945046
|
entity |
| Predicate | leadershipIncludes |
P9741
|
FINISHED |
| Object | Brother Jack |
—
|
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: Brother Jack | Statement: [the Brotherhood (Invisible Man), leadershipIncludes, Brother Jack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadershipIncludes Context triple: [the Brotherhood (Invisible Man), leadershipIncludes, Brother Jack]
-
A.
includedLeader
chosen
Indicates that an entity is recognized or designated as a leader within a specified group, set, or collection.
-
B.
leadershipContext
Indicates the situational or organizational setting in which leadership is exercised or expressed between entities.
-
C.
documentsLeadership
Indicates that one entity records, evidences, or provides authoritative documentation of another entity’s leadership or leadership role.
-
D.
involvesLeader
Indicates that the relationship or action includes or is carried out by an entity serving in a leadership role.
-
E.
leadershipFocus
Indicates a relationship where an entity’s attention, priorities, or strategic efforts are directed toward leading, guiding, or influencing others.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:19 p.m.