Triple
T24916355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HERA |
E623995
|
entity |
| Predicate | primaryCollisionType |
P5342
|
FINISHED |
| Object | electron–proton |
—
|
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: electron–proton | Statement: [HERA, primaryCollisionType, electron–proton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCollisionType Context triple: [HERA, primaryCollisionType, electron–proton]
-
A.
collisionType
chosen
Indicates the specific kind or category of collision that occurs between two or more entities.
-
B.
marksCollisionBetween
Indicates a recorded event or state where two or more entities have come into contact or collided with each other.
-
C.
primaryDamageType
Indicates the main kind of harm or injury that an action, event, or object is responsible for causing.
-
D.
collision
Indicates that two or more entities come into contact with each other at the same place and time, typically involving an impact or crash.
-
E.
primaryEventType
Indicates the main or most significant category of event with which an entity, record, or occurrence is primarily associated.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 18, 2026, 5:28 a.m.