Triple

T38242064
Position Surface form Disambiguated ID Type / Status
Subject Ravka E1013791 entity
Predicate hasEliteGuard P114815 FINISHED
Object King’s Guard 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: King’s Guard | Statement: [Ravka, hasEliteGuard, King’s Guard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEliteGuard
Context triple: [Ravka, hasEliteGuard, King’s Guard]
  • A. isEliteUnit
    Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
  • B. isEliteSquad
    Indicates that a group or unit is recognized as a top-tier, highly skilled, and specially selected squad within a larger organization or force.
  • C. hasRoyalGuard chosen
    Indicates that an entity is protected or served by a designated royal guard or group of royal guards.
  • D. hasStarGuard
    Indicates that an entity is protected or overseen by a designated star-related guardian or protective force.
  • E. hasEliteLanguage
    Indicates that an entity uses or is associated with a language variety considered elite, prestigious, or high-status within a given context.
  • 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_69f76dd72a248190a5fe18db2bd1eb15 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd231cab588190ad0953dc8f4af8f2 completed May 7, 2026, 11:41 p.m.
PD Predicate disambiguation batch_69fd1aa3f1c481909fe6e9cab1383551 completed May 7, 2026, 11:05 p.m.
Created at: May 3, 2026, 4:30 p.m.