Triple

T38589840
Position Surface form Disambiguated ID Type / Status
Subject Firemaw E932427 entity
Predicate encounterRole P186807 FINISHED
Object gear and coordination check for raiding guilds 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: gear and coordination check for raiding guilds | Statement: [Firemaw, encounterRole, gear and coordination check for raiding guilds]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: encounterRole
Context triple: [Firemaw, encounterRole, gear and coordination check for raiding guilds]
  • A. teamRoleInEncounters chosen
    Indicates the specific role an entity holds within a team during particular encounters or interactions.
  • B. clinicalRole
    Indicates the specific function, responsibility, or position an entity holds within a clinical or healthcare context.
  • C. hasPatientRole
    Indicates that an entity participates in a relationship or activity specifically in the role of a patient (the one receiving care, treatment, or action).
  • D. encounterLocation
    Indicates the place or setting where two or more entities meet, interact, or come into contact.
  • E. encodingRole
    Indicates the role or function an entity has in the process of encoding information into a particular form or representation.
  • 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_69fcdfbc71c481908ba7f87907b17782 completed May 7, 2026, 6:53 p.m.
PD Predicate disambiguation batch_69fcdbe580b8819087f143596b2c79c0 completed May 7, 2026, 6:37 p.m.
Created at: May 3, 2026, 4:32 p.m.