Triple

T14506453
Position Surface form Disambiguated ID Type / Status
Subject Penrose spin networks E340275 entity
Predicate vertexCondition P114496 FINISHED
Object angular momentum coupling rule 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: angular momentum coupling rule | Statement: [Penrose spin networks, vertexCondition, angular momentum coupling rule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vertexCondition
Context triple: [Penrose spin networks, vertexCondition, angular momentum coupling rule]
  • A. angleCondition
    Indicates that a specified geometric relationship holds between angles, such as equality, inequality, or a particular angular constraint.
  • B. variableCondition
    Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
  • C. entryCondition
    Indicates the prerequisite state, criteria, or circumstances that must be satisfied before entering or initiating a particular process, state, or context.
  • D. containsCondition
    Indicates that one entity includes, embodies, or is associated with a particular condition.
  • E. coreCondition
    Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
  • 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_69d822d9c0408190b9a2b3643e58bb4d completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69de94e25a2481908b8394e9a19f3b64 completed April 14, 2026, 7:26 p.m.
PD Predicate disambiguation batch_69de5c4ccba08190a988bfda0bc9f5cb completed April 14, 2026, 3:25 p.m.
PDg Predicate description generation batch_69de5fb4de14819092acdecbd201d672 completed April 14, 2026, 3:39 p.m.
Created at: April 10, 2026, 1:21 a.m.