Triple

T26345770
Position Surface form Disambiguated ID Type / Status
Subject CSS shapes E662773 entity
Predicate shapeMarginControls P15873 FINISHED
Object distance between the shape and wrapped content 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: distance between the shape and wrapped content | Statement: [CSS shapes, shapeMarginControls, distance between the shape and wrapped content]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shapeMarginControls
Context triple: [CSS shapes, shapeMarginControls, distance between the shape and wrapped content]
  • A. leafMargin
    Indicates the type or pattern of the edge or border of a leaf (e.g., smooth, serrated, lobed).
  • B. marginStyle chosen
    Indicates how the margins around an element are styled or configured in relation to surrounding content.
  • C. hasOwnBorderControls
    Indicates that an entity independently manages and enforces its own border control policies and procedures, separate from those of other entities.
  • D. isMarginable
    Indicates that a financial asset or position can be used as collateral for borrowing funds or trading on margin.
  • E. formsBorderWithin
    Indicates that one entity constitutes a boundary or border located entirely within the spatial extent of another entity.
  • 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_69ee81304194819092e20e0fae3aee07 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f61f12b0f08190bc4a16907941864c completed May 2, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69f61b3a8ae0819090189fbd8eb19f2f completed May 2, 2026, 3:41 p.m.
Created at: April 26, 2026, 10:42 p.m.