Triple
T1095984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drell–Yan processes |
E24272
|
entity |
| Predicate | interactionType |
P3663
|
FINISHED |
| Object | quark–antiquark annihilation |
—
|
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: quark–antiquark annihilation | Statement: [Drell–Yan processes, interactionType, quark–antiquark annihilation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionType Context triple: [Drell–Yan processes, interactionType, quark–antiquark annihilation]
-
A.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
B.
engagementType
chosen
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
C.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
D.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
E.
dialogueWith
Indicates that two entities are engaged in a mutual conversational exchange or dialogue with each other.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.