Triple

T29389238
Position Surface form Disambiguated ID Type / Status
Subject PrintDocumentAdapter E745331 entity
Predicate onLayout P166711 FINISHED
Object calledOnLayoutOrAttributesChange 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: calledOnLayoutOrAttributesChange | Statement: [PrintDocumentAdapter, onLayout, calledOnLayoutOrAttributesChange]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: onLayout
Context triple: [PrintDocumentAdapter, onLayout, calledOnLayoutOrAttributesChange]
  • A. basedOnLayout
    Indicates that one entity is derived from, structured according to, or determined by the layout or spatial arrangement defined by another entity.
  • B. hasLayout
    Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
  • C. layoutEngine
    Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
  • D. laidOutBy
    Indicates that one entity has been arranged, organized, or presented in a particular layout or structure by another entity.
  • E. layoutShape
    Indicates a spatial or structural arrangement relationship where one entity defines or influences the geometric shape or configuration of another.
  • 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_69f0a79dfabc81908755382ee47791e2 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f669d578608190962d35116a01420c completed May 2, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69f660f4f7a88190b93c60d76b86c912 completed May 2, 2026, 8:39 p.m.
PDg Predicate description generation batch_69f661b47d088190934f63884a203261 completed May 2, 2026, 8:42 p.m.
Created at: April 28, 2026, 2:41 p.m.