Triple

T37462881
Position Surface form Disambiguated ID Type / Status
Subject Gentle Megasaur E930961 entity
Predicate tribeSynergyType P187886 FINISHED
Object board buff 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: board buff | Statement: [Gentle Megasaur, tribeSynergyType, board buff]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tribeSynergyType
Context triple: [Gentle Megasaur, tribeSynergyType, board buff]
  • A. tribeSynergy chosen
    Indicates a cooperative or mutually enhancing relationship among members of the same tribe or group, where their combined presence or actions produce greater overall effectiveness than they would individually.
  • B. classTribeSynergy
    Indicates a synergistic relationship where a character’s class and tribe traits interact to provide combined or enhanced effects.
  • C. inTribe
    Indicates that an entity belongs to, is a member of, or is affiliated with a particular tribe.
  • D. includesTribe
    Indicates that one entity contains, encompasses, or has within it a particular tribe as a member or component.
  • E. tribalStandardAssociatedWith
    Indicates a relationship where a tribal standard (such as a flag, emblem, or banner) is associated with, represents, or belongs to a particular tribe or tribal group.
  • 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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbc36ce1f88190a7fa1656b714e107 completed May 6, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69fbbd13595c81908719f52c3d37a7e8 completed May 6, 2026, 10:13 p.m.
Created at: May 3, 2026, 4:17 p.m.