Triple
T35149481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Dana Fairbank |
E1014944
|
entity |
| Predicate | hasLeadershipRoleSince |
P196101
|
FINISHED |
| Object | 1990s (leadership at Capital One) |
—
|
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: 1990s (leadership at Capital One) | Statement: [Richard Dana Fairbank, hasLeadershipRoleSince, 1990s (leadership at Capital One)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadershipRoleSince Context triple: [Richard Dana Fairbank, hasLeadershipRoleSince, 1990s (leadership at Capital One)]
-
A.
hasLeadershipFunction
Indicates that an entity holds or performs a leadership role, responsibility, or function in relation to another entity or context.
-
B.
hasLeadershipExperienceIn
Indicates that an entity possesses prior leadership experience specifically within a given domain, context, or organization.
-
C.
hasLeaderHeldOffice
Indicates that the specified leader has occupied or served in an official office or position.
-
D.
leadershipRoleOn
Indicates that one entity holds a leadership position or role with respect to another entity.
-
E.
hadLeadershipFrom
Indicates that one entity received leadership, guidance, or direction from another entity.
- F. None of above. chosen
Provenance (4 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:02 p.m.