Triple
T38593126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Morrison |
E932498
|
entity |
| Predicate | organizationLeadership |
P3459
|
FINISHED |
| Object | Overwatch |
—
|
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: Overwatch | Statement: [Jack Morrison, organizationLeadership, Overwatch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationLeadership Context triple: [Jack Morrison, organizationLeadership, Overwatch]
-
A.
organizationLed
Indicates that one organization provides leadership, direction, or governance over another organization or collective effort.
-
B.
documentsLeadership
Indicates that one entity records, evidences, or provides authoritative documentation of another entity’s leadership or leadership role.
-
C.
leadershipContext
Indicates the situational or organizational setting in which leadership is exercised or expressed between entities.
-
D.
leadershipPosition
chosen
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
E.
organizedDuringLeadershipOf
Indicates that an event or activity was organized while a specific person or group held a leadership position.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:32 p.m.