Triple

T2785770
Position Surface form Disambiguated ID Type / Status
Subject ASTM C150 E61805 entity
Predicate conformsWith P3994 FINISHED
Object ASTM International consensus process 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: ASTM International consensus process | Statement: [ASTM C150, conformsWith, ASTM International consensus process]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conformsWith
Context triple: [ASTM C150, conformsWith, ASTM International consensus process]
  • A. conformsTo chosen
    Indicates that one entity complies with, follows, or is in accordance with a specified standard, specification, rule, or guideline.
  • B. coincidesWith
    Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
  • C. indicatesComplianceWith
    Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
  • D. consistentWith
    Indicates that one entity does not contradict and is compatible or in agreement with another entity, condition, or set of constraints.
  • E. hasConformanceRequirements
    Indicates that an entity is subject to specific rules, standards, or criteria that it must satisfy or comply with.
  • 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_69ab4b7f51d881908768300ebd2fbdae completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdeea881481908d759c72798a50fb completed March 7, 2026, 8:16 a.m.
PD Predicate disambiguation batch_69abdd025c948190a97dd961a9592bac completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:57 p.m.