Triple

T26201309
Position Surface form Disambiguated ID Type / Status
Subject Zerbaghali E655236 entity
Predicate isTunable P81276 FINISHED
Object true 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: true | Statement: [Zerbaghali, isTunable, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTunable
Context triple: [Zerbaghali, isTunable, true]
  • A. tunable chosen
    Indicates that the associated entity can be adjusted or configured to different settings or values, typically to optimize performance or behavior.
  • B. isTunedTo
    Indicates that one entity has been adjusted or configured to operate at, receive, or correspond to the frequency, channel, or setting of another entity.
  • C. tuningType
    Indicates the specific method or configuration by which something is adjusted or calibrated to achieve a desired performance or behavior.
  • D. supportsWeaponTuning
    Indicates that an entity provides the capability to adjust, modify, or customize the characteristics or performance of a weapon.
  • E. tunedOrUntuned
    Indicates whether something is in a properly adjusted or calibrated state (tuned) or not (untuned).
  • 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_69ee5b48236c81908fe385b6afc4f60b completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60cdba6248190b34176bc568e7697 completed May 2, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69f5b007ec1c819092e2c3605933f60b completed May 2, 2026, 8:04 a.m.
Created at: April 26, 2026, 8:48 p.m.