Triple

T6482389
Position Surface form Disambiguated ID Type / Status
Subject newton E146424 entity
Predicate isCoherentWith P29598 FINISHED
Object joule 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: joule | Statement: [newton, isCoherentWith, joule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCoherentWith
Context triple: [newton, isCoherentWith, joule]
  • A. isEquiconsistentWith
    Indicates that two formal theories or systems have the same consistency strength, such that if one is consistent then the other is also consistent, and if one is inconsistent then so is the other.
  • B. coincidesWith
    Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
  • C. isCanonicalFormOf
    Indicates that one entity is the standard or officially accepted form or representation of another, often more variant, entity.
  • D. isIsomorphicTo
    Indicates that two structures have a one-to-one, structure-preserving correspondence between their elements, making them equivalent in form even if not identical in content.
  • E. consistentWith chosen
    Indicates that one entity does not contradict and is compatible or in agreement with another entity, condition, or set of constraints.
  • 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_69c0090158c08190af0df9a2348d2d52 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a6b2e9881908b715573e7ba7458 completed March 22, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69c0673f6d48819080e10c85155c7195 completed March 22, 2026, 10:03 p.m.
Created at: March 22, 2026, 4:51 p.m.