Triple
T18425172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cam Neely |
E442118
|
entity |
| Predicate | teamLeadershipRole |
P3459
|
FINISHED |
| Object | franchise icon |
—
|
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: franchise icon | Statement: [Cam Neely, teamLeadershipRole, franchise icon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLeadershipRole Context triple: [Cam Neely, teamLeadershipRole, franchise icon]
-
A.
teamLead
Indicates that one entity serves as the leader or primary coordinator of a team that includes the other entity.
-
B.
leadershipRolesOverseenBy
Indicates that certain leadership roles are supervised, managed, or overseen by a specified entity.
-
C.
leadershipPosition
chosen
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
D.
notableTeamLeader
Indicates that an entity serves as a prominent or distinguished leader of a particular team.
-
E.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51b1149788190ad7c453547a6e07c |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.