Triple

T3309814
Position Surface form Disambiguated ID Type / Status
Subject Alphonse Capone E69542 entity
Predicate notableAliasOrigin P25214 FINISHED
Object nickname "Scarface" due to facial scars from a knife attack 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: nickname "Scarface" due to facial scars from a knife attack | Statement: [Alphonse Capone, notableAliasOrigin, nickname "Scarface" due to facial scars from a knife attack]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableAliasOrigin
Context triple: [Alphonse Capone, notableAliasOrigin, nickname "Scarface" due to facial scars from a knife attack]
  • A. notableNickname chosen
    Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
  • B. alsoKnownAs
    Indicates that one entity is an alternative name, alias, or designation for another entity.
  • C. notablyAssociatedWith
    Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
  • D. notableTarget
    Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
  • E. associatedName
    Indicates that one entity has an alternative or related name that is linked or connected to another entity.
  • 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_69ad859f218081909458d2cebbf57565 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb0eb6dd08190bab1ce80f417966a completed March 8, 2026, 5:24 p.m.
PD Predicate disambiguation batch_69ada4282730819092aa39c5f9269df0 completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:11 p.m.