Triple

T23737935
Position Surface form Disambiguated ID Type / Status
Subject heterotic supergravity E586586 entity
Predicate requiresConstraint P100 FINISHED
Object Bianchi identity for H-field 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: Bianchi identity for H-field | Statement: [heterotic supergravity, requiresConstraint, Bianchi identity for H-field]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresConstraint
Context triple: [heterotic supergravity, requiresConstraint, Bianchi identity for H-field]
  • A. supportsConstraint
    Indicates that one entity upholds, enforces, or is compatible with a specified constraint or set of constraints in relation to another entity.
  • B. constrainedBy
    Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
  • C. requiredBy
    Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
  • D. requires chosen
    Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
  • E. requiredOn
    Indicates that one entity must exist, be present, or be fulfilled on a specific other entity, date, or condition as a mandatory requirement.
  • 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_69e24907dc9c8190be074c9c96a0ec2d completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bad356c88190ae29ce403145ee73 completed April 29, 2026, 8:01 a.m.
PD Predicate disambiguation batch_69f155f012808190a4b1cbc155558ade completed April 29, 2026, 12:50 a.m.
Created at: April 17, 2026, 7:11 p.m.