Triple

T32549987
Position Surface form Disambiguated ID Type / Status
Subject alvinkamara E831946 entity
Predicate hasLinkTo P180731 FINISHED
Object Alvin Kamara-related brands or partnerships 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: Alvin Kamara-related brands or partnerships | Statement: [alvinkamara, hasLinkTo, Alvin Kamara-related brands or partnerships]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLinkTo
Context triple: [alvinkamara, hasLinkTo, Alvin Kamara-related brands or partnerships]
  • A. hasBeenLinkedTo chosen
    Indicates that an entity has been associated or connected with another entity, often suggesting a reported or inferred relationship between them.
  • B. canBeLinkedTo
    Indicates that one entity has the potential or capability to be connected or associated with another entity.
  • C. hasExternalLink
    Indicates that an entity is associated with a hyperlink pointing to a resource outside the current system or domain.
  • D. hasRelation
    Indicates that there exists some specified relationship or association between two entities.
  • E. hasDeepLevelLink
    Indicates a relationship where one entity is connected to another through a non-obvious, nested, or lower-level link within a hierarchical or layered structure.
  • 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_69f34925fd08819084cfe4ec566cb704 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fdbaa226708190b8ed96e93aad38de completed May 8, 2026, 10:27 a.m.
PD Predicate disambiguation batch_69fdb58b07e48190837e00966de050d4 completed May 8, 2026, 10:06 a.m.
Created at: May 1, 2026, 1:02 a.m.