Triple

T3919042
Position Surface form Disambiguated ID Type / Status
Subject PIXL E88913 entity
Predicate spatialResolution P25684 FINISHED
Object microscopic scale 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: microscopic scale | Statement: [PIXL, spatialResolution, microscopic scale]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: spatialResolution
Context triple: [PIXL, spatialResolution, microscopic scale]
  • A. hasSpatialResolution chosen
    Indicates that something is characterized by a specific level of spatial detail or granularity at which it can represent or distinguish features in space.
  • B. sensorResolution
    Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
  • C. spectralResolution
    Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
  • D. typicalResolution
    Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
  • E. pixelScale
    Indicates the ratio or conversion factor between pixel units and real-world or coordinate-space units in a representation or image.
  • 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_69aed955229881909e85e73ffab1d343 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef188b474819087680db42b04ecdd completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee75eedcc81908088ff4dbb8be56b completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:22 p.m.