Triple

T36491805
Position Surface form Disambiguated ID Type / Status
Subject miniImageNet E899067 entity
Predicate hasBenchmarkProperty P131257 FINISHED
Object supports reproducible few-shot experiments 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: supports reproducible few-shot experiments | Statement: [miniImageNet, hasBenchmarkProperty, supports reproducible few-shot experiments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBenchmarkProperty
Context triple: [miniImageNet, hasBenchmarkProperty, supports reproducible few-shot experiments]
  • A. hasBenchmarkInstances
    Indicates that an entity is associated with one or more benchmark instances used for evaluation or comparison.
  • B. hasBenchmarkRole
    Indicates that an entity holds or is assigned a specific role within a benchmarking context or process.
  • C. benchmarkProperty chosen
    Indicates that a property or attribute is being used as a benchmark or reference standard for evaluating or comparing other entities or values.
  • D. benchmarksAre
    Indicates that one entity serves as a performance or quality benchmark or standard of comparison for another entity.
  • E. haveProperty
    Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
  • 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_69f76e5ad4588190bdbce60c52fbb785 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fd0b92f42881908cd77e3f058adcc2 completed May 7, 2026, 10 p.m.
PD Predicate disambiguation batch_69fd0a3d68d4819094d92040f7c48d7c completed May 7, 2026, 9:55 p.m.
Created at: May 3, 2026, 4:10 p.m.