Triple
T37729287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemar Hoskins |
E940112
|
entity |
| Predicate | servedAsSidekickTo |
P91347
|
FINISHED |
| Object | John Walker |
—
|
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: John Walker | Statement: [Lemar Hoskins, servedAsSidekickTo, John Walker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsSidekickTo Context triple: [Lemar Hoskins, servedAsSidekickTo, John Walker]
-
A.
formerSidekick
chosen
Indicates that one entity previously served as a sidekick or subordinate companion to another entity, but no longer holds that role.
-
B.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
C.
playedAlongside
Indicates that two or more entities participated together at the same time in a shared activity, performance, or event.
-
D.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
E.
sidekickRealName
Indicates the real, non-superhero identity of a sidekick character.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
Created at: May 3, 2026, 4:18 p.m.