Triple

T25987101
Position Surface form Disambiguated ID Type / Status
Subject Maggie Rhee (reluctant, Dead City) E646230 entity
Predicate hasSurvivalSkill P175954 FINISHED
Object combat 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: combat | Statement: [Maggie Rhee (reluctant, Dead City), hasSurvivalSkill, combat]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSurvivalSkill
Context triple: [Maggie Rhee (reluctant, Dead City), hasSurvivalSkill, combat]
  • A. hasSurvivabilityFeature
    Indicates that an entity possesses a characteristic, design element, or capability intended to enhance its ability to endure, resist damage, or remain functional under adverse conditions.
  • B. survivesWith
    Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
  • C. killsAt
    Indicates that one entity causes the death of another entity at a specific time or event.
  • D. believedToHaveAbility
    Indicates that one entity is thought or assumed to possess a particular capability or power, without asserting that the ability is actually verified.
  • E. survivesIn
    Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
  • F. None of above. chosen

Provenance (4 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_69e77e881fc08190ba1c8dc7e2a07f97 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f6db3606808190a80c6e9f5da5b33e completed May 3, 2026, 5:20 a.m.
PD Predicate disambiguation batch_69f6d82adfa481908a5e196d2e18c73f completed May 3, 2026, 5:07 a.m.
PDg Predicate description generation batch_69f6db1bc348819097c844f76e2fa4fe completed May 3, 2026, 5:20 a.m.
Created at: April 22, 2026, 8:55 a.m.