Triple
T1160888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NA61/SHINE |
E24486
|
entity |
| Predicate | usesProjectile |
P1454
|
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: [NA61/SHINE, usesProjectile, protons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProjectile Context triple: [NA61/SHINE, usesProjectile, protons]
-
A.
involvesProjectile
chosen
Indicates that the action or event includes the use, presence, or motion of a projectile as a key component of the interaction between entities.
-
B.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
C.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
D.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
-
E.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb1915081908834ced85d09e299 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.