Triple

T38590997
Position Surface form Disambiguated ID Type / Status
Subject Hrothgar E932451 entity
Predicate canBePlayerJob P27683 FINISHED
Object any combat job allowed to their race 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: any combat job allowed to their race | Statement: [Hrothgar, canBePlayerJob, any combat job allowed to their race]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBePlayerJob
Context triple: [Hrothgar, canBePlayerJob, any combat job allowed to their race]
  • A. canBeHiredFor
    Indicates that one entity is eligible or suitable to be employed or contracted by another entity for a particular role, task, or position.
  • B. hasPlayingRole
    Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
  • C. canBeEarnedBy
    Indicates that something (such as a reward, status, or resource) is obtainable through the actions, efforts, or qualifications of a particular entity.
  • D. isRecruitableCharacter
    Indicates that a character can be obtained and added to the player’s controllable roster or party.
  • E. canBeAssignedTo chosen
    Indicates that one entity is eligible or permitted to be allocated, designated, or linked to another entity for a particular purpose or role.
  • 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_69f76ec654d48190b421111cf26e54d9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ffbf84f4948190b41a7bba07ae61ec completed May 9, 2026, 11:13 p.m.
PD Predicate disambiguation batch_69ffbf0a59f88190870dbe25d8a63a00 completed May 9, 2026, 11:11 p.m.
Created at: May 3, 2026, 4:32 p.m.