Triple

T13590615
Position Surface form Disambiguated ID Type / Status
Subject Aspect experiment on Bell inequality tests (1982) E324682 entity
Predicate addressesLoophole P103646 FINISHED
Object locality loophole (partially) 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: locality loophole (partially) | Statement: [Aspect experiment on Bell inequality tests (1982), addressesLoophole, locality loophole (partially)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: addressesLoophole
Context triple: [Aspect experiment on Bell inequality tests (1982), addressesLoophole, locality loophole (partially)]
  • A. addresses
    Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
  • B. addressedThrough
    Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
  • C. locationAddressed
    Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
  • D. addressesPosition
    Indicates that one entity communicates with, responds to, or deals with the role, status, or job position held by another entity.
  • E. helpsAddress chosen
    Indicates that one entity contributes to solving, mitigating, or dealing with an issue, need, or problem associated with another entity.
  • 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_69d80769eaf081909d82f44e484d6113 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb055cc98819091fab597b69e5e3e completed April 12, 2026, 2:46 p.m.
PD Predicate disambiguation batch_69dbae18eaf48190809e8b365856cde9 completed April 12, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:49 p.m.