Triple

T21003177
Position Surface form Disambiguated ID Type / Status
Subject BNL E852 E517345 entity
Predicate usedInstrumentation P142440 FINISHED
Object tracking detectors 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: tracking detectors | Statement: [BNL E852, usedInstrumentation, tracking detectors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInstrumentation
Context triple: [BNL E852, usedInstrumentation, tracking detectors]
  • A. hasInstrumentationProvidedBy
    Indicates that the instrumentation used in an activity, process, or work is supplied or made available by a specified provider.
  • B. originalInstrumentationNotFullySpecified
    Indicates that the original instrumentation involved in an event or work is only partially known or not completely specified.
  • C. originalInstrumentation
    Indicates the relationship between a musical work and the specific instruments or ensemble for which it was initially scored or conceived.
  • D. usesInstrument
    Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
  • E. compiledUsingInstrument
    Indicates that a software artifact was compiled by using a particular tool, device, or instrument as part of the compilation process.
  • 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_69e0b50192308190a284fcc89dd23a49 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc38b8688190860fba1b58e1b3e6 completed April 21, 2026, 4:25 a.m.
PD Predicate disambiguation batch_69e5dbec80708190a49bccab7ff97e7b completed April 20, 2026, 7:55 a.m.
PDg Predicate description generation batch_69e5e2df1a888190b5b478e76bdf7fdf completed April 20, 2026, 8:25 a.m.
Created at: April 16, 2026, 1:52 p.m.