Triple

T35332241
Position Surface form Disambiguated ID Type / Status
Subject Bloch wall E1020352 entity
Predicate hasPhysicalQuantity P187087 FINISHED
Object wall thickness 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: wall thickness | Statement: [Bloch wall, hasPhysicalQuantity, wall thickness]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPhysicalQuantity
Context triple: [Bloch wall, hasPhysicalQuantity, wall thickness]
  • A. hasPhysicalQuantityType
    Indicates that an entity is associated with, or characterized by, a specific type or category of physical quantity (such as length, mass, time, or temperature).
  • B. belongsToPhysicalQuantity
    Indicates that one entity is a component, attribute, or part of a specific physical quantity, linking it to that quantity as its owner or container.
  • C. isScalarQuantity
    Indicates that the related physical quantity has only magnitude and no directional component.
  • D. estimatedPhysicalQuantity
    Indicates that a physical quantity is not directly measured but inferred or approximated based on available data or calculations.
  • E. hasPhysicalMeaning
    Indicates that something possesses a well-defined, interpretable significance in terms of physical concepts, quantities, or phenomena.
  • 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_69f76deacf4481908e7735a5a7715b0a completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fb3425666081908916fcbf3b5dd907 completed May 6, 2026, 12:29 p.m.
PD Predicate disambiguation batch_69fb2f5f3164819099429c2cc3d24e01 completed May 6, 2026, 12:09 p.m.
PDg Predicate description generation batch_69fb3424724c8190ba55ecf66fa0b171 completed May 6, 2026, 12:29 p.m.
Created at: May 3, 2026, 4:03 p.m.