Triple

T23281123
Position Surface form Disambiguated ID Type / Status
Subject combinatory logic E588865 entity
Predicate hasNormalFormConcept P151656 FINISHED
Object normal form of a combinatory term 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: normal form of a combinatory term | Statement: [combinatory logic, hasNormalFormConcept, normal form of a combinatory term]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNormalFormConcept
Context triple: [combinatory logic, hasNormalFormConcept, normal form of a combinatory term]
  • A. hasCanonicalFormulation
    Indicates that one entity is the standard or officially accepted formulation or expression of another entity.
  • B. isCanonicalFormOf
    Indicates that one entity is the standard or officially accepted form or representation of another, often more variant, entity.
  • C. hasNorm
    Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
  • D. hasNonStandardForm
    Indicates that an entity possesses a form, variant, or representation that deviates from the standard, canonical, or commonly accepted form.
  • E. hasNaturalForm
    Indicates that an entity possesses an inherent, unaltered, or naturally occurring form or state.
  • 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_69e25d16e2c08190a291de254703129e completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f19642b46481909fd455acd2155792 completed April 29, 2026, 5:25 a.m.
PD Predicate disambiguation batch_69effcecabd88190856fb6e1d993e4dd completed April 28, 2026, 12:18 a.m.
PDg Predicate description generation batch_69f01d8770d081908897c28b04e5faea completed April 28, 2026, 2:37 a.m.
Created at: April 17, 2026, 4:57 p.m.