Triple
T30528142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Wynn-Jones |
E776913
|
entity |
| Predicate | sharesLeadershipRoleAt |
P13957
|
FINISHED |
| Object | Norwich City F.C. |
—
|
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: Norwich City F.C. | Statement: [Michael Wynn-Jones, sharesLeadershipRoleAt, Norwich City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLeadershipRoleAt Context triple: [Michael Wynn-Jones, sharesLeadershipRoleAt, Norwich City F.C.]
-
A.
leadershipRoleOn
Indicates that one entity holds a leadership position or role with respect to another entity.
-
B.
sharesLeadershipWith
Indicates that two entities jointly hold or participate in leadership roles or responsibilities, sharing authority or decision-making power.
-
C.
partnerInLeadershipWith
Indicates that two entities share a joint leadership role or responsibility, collaborating as partners in guiding or managing an organization, group, or initiative.
-
D.
leadershipRolesOverseenBy
Indicates that certain leadership roles are supervised, managed, or overseen by a specified entity.
-
E.
hasOrganizationalRole
chosen
Indicates that an entity holds a specific role, position, or function within an organization.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 29, 2026, 8:18 p.m.