Triple

T4828426
Position Surface form Disambiguated ID Type / Status
Subject Stanford Linear Collider E107881 entity
Predicate beamAccelerationMethod P25433 FINISHED
Object radio‑frequency linear acceleration 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: radio‑frequency linear acceleration | Statement: [Stanford Linear Collider, beamAccelerationMethod, radio‑frequency linear acceleration]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: beamAccelerationMethod
Context triple: [Stanford Linear Collider, beamAccelerationMethod, radio‑frequency linear acceleration]
  • A. beamDynamicsFeature
    Indicates a characteristic or aspect related to the behavior, motion, or interaction of beams within a dynamic system.
  • B. beamParticle
    Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
  • C. beamExtractionMethod chosen
    Indicates the method or technique used to extract or generate a beam from a source.
  • D. beamCurrent
    Indicates the amount of electric current carried by a directed beam (such as a particle or electron beam) in a system or experiment.
  • E. beamLine
    Indicates a relationship where one entity directs or projects a beam or focused line (such as light, energy, or signal) toward 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_69bd43fac8188190803f0327190621e4 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ddd17d881909f7731ff2b460e83 completed March 20, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69bd6c1fe130819087ae01309f96a0c8 completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:24 p.m.