Triple
T551920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LHC injector chain |
E11858
|
entity |
| Predicate | usesParticleType |
P3639
|
FINISHED |
| Object | protons |
—
|
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: protons | Statement: [LHC injector chain, usesParticleType, protons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesParticleType Context triple: [LHC injector chain, usesParticleType, protons]
-
A.
hasParticleType
chosen
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
-
B.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
-
C.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
D.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
E.
hasPetrovType
Indicates that an entity (typically a spacetime or gravitational field) is classified as having a specific Petrov type in the Petrov classification of its Weyl tensor.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499047bd4819089ca8345f1b6e46c |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.