Triple
T18548942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bart Nickerson |
E453314
|
entity |
| Predicate | roleInYellowjackets |
P42172
|
FINISHED |
| Object | co-creator |
—
|
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: co-creator | Statement: [Bart Nickerson, roleInYellowjackets, co-creator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInYellowjackets Context triple: [Bart Nickerson, roleInYellowjackets, co-creator]
-
A.
roleInSeason
Indicates the specific role or function an entity has within a particular season of a series or competition.
-
B.
roleAtSportsTeam
Indicates the specific position or function an individual holds within a sports team.
-
C.
playsInRole
chosen
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
roleInFranchiseHistory
Indicates the specific function, position, or contribution an entity has within the historical development or timeline of a franchise.
-
E.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534be2298819095f637065fc2724e |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.