Triple

T18016870
Position Surface form Disambiguated ID Type / Status
Subject seaborn.set_context E431016 entity
Predicate contextLevel(notebook) P129428 FINISHED
Object medium base element sizes 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: medium base element sizes | Statement: [seaborn.set_context, contextLevel(notebook), medium base element sizes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: contextLevel(notebook)
Context triple: [seaborn.set_context, contextLevel(notebook), medium base element sizes]
  • A. notabilityScope
    Indicates the domain, field, or context within which something is considered notable or significant.
  • B. isNotebookOf
    Indicates that one entity is a notebook that belongs to, is used by, or is associated with another entity.
  • C. notableLevel
    Indicates the degree or extent to which something is considered notable or significant.
  • D. navigationNote
    Indicates that there is an auxiliary note or instruction intended to guide or assist navigation within a resource, interface, or environment.
  • E. classificationLevel
    Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
  • F. None of above. chosen

Provenance (4 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b9be5d0c819097e006f32d98753a completed April 19, 2026, 11:17 a.m.
PD Predicate disambiguation batch_69e3f904b8048190add43883cd7cb191 completed April 18, 2026, 9:35 p.m.
PDg Predicate description generation batch_69e42d8eefa88190a700c7c1b4213e46 completed April 19, 2026, 1:19 a.m.
Created at: April 10, 2026, 10:24 a.m.