Triple

T33588712
Position Surface form Disambiguated ID Type / Status
Subject Wilson loop E860358 entity
Predicate hasExpectationValueBehavior P152810 FINISHED
Object area law in confining phases 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: area law in confining phases | Statement: [Wilson loop, hasExpectationValueBehavior, area law in confining phases]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExpectationValueBehavior
Context triple: [Wilson loop, hasExpectationValueBehavior, area law in confining phases]
  • A. expectedValue chosen
    Indicates the predicted or average outcome of a variable or event, typically computed as a probability-weighted sum of all possible values.
  • B. hasStabilityExpectation
    Indicates that one entity expects another entity to maintain a certain level or condition of stability over time.
  • C. hasTemporalExpectation
    Indicates that one entity holds an expectation about when (in time) another event, state, or action will occur or be valid.
  • D. hasAudienceExpectation
    Indicates that one entity holds assumptions or anticipates certain reactions, knowledge, or behavior from its audience in relation to another entity or context.
  • E. setsExpectationsFor
    Indicates that one entity defines or communicates standards, requirements, or anticipated outcomes that another entity is expected to meet or follow.
  • 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_69f3497e70e48190951c94d072879bec completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fce7671f108190bf3ebf54339068b5 completed May 7, 2026, 7:26 p.m.
PD Predicate disambiguation batch_69fce5b5a84c81908ac1b5b9f08d48d0 completed May 7, 2026, 7:19 p.m.
Created at: May 1, 2026, 1:40 a.m.