Triple

T16096516
Position Surface form Disambiguated ID Type / Status
Subject Garris Shrike E390496 entity
Predicate relationshipToHanSolo P38921 FINISHED
Object abusive foster guardian 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: abusive foster guardian | Statement: [Garris Shrike, relationshipToHanSolo, abusive foster guardian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationshipToHanSolo
Context triple: [Garris Shrike, relationshipToHanSolo, abusive foster guardian]
  • A. relationshipToTheDude
    Indicates the specific type of personal or social relationship that one entity has to the individual referred to as "the Dude."
  • B. relationshipToCharacter chosen
    Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
  • C. relationshipToMarvelUniverse
    Indicates the nature or type of connection an entity has to the Marvel universe, such as affiliation, role, or relevance within that fictional setting.
  • D. relationshipToTony
    Indicates the specific type of relationship or connection that an entity has with Tony.
  • E. relationshipToRelative
    Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
  • 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_69d87f198bc48190a8b7e53ca15b7ead completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e1ff63edb0819092cbb671967bbdcd completed April 17, 2026, 9:37 a.m.
PD Predicate disambiguation batch_69e182804208819087f35307cd6e4103 completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 4:59 a.m.