Triple
T3616292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDF detector |
E76606
|
entity |
| Predicate | topQuarkDiscoveryContext |
P20031
|
FINISHED |
| Object | proton–antiproton collisions at the Tevatron |
—
|
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: proton–antiproton collisions at the Tevatron | Statement: [CDF detector, topQuarkDiscoveryContext, proton–antiproton collisions at the Tevatron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topQuarkDiscoveryContext Context triple: [CDF detector, topQuarkDiscoveryContext, proton–antiproton collisions at the Tevatron]
-
A.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
B.
emergedInContext
chosen
Indicates that something came into existence, became apparent, or developed within a specific situation, environment, or set of circumstances.
-
C.
coDiscovererOf
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
D.
maximumProtonProtonCentreOfMassEnergy
Indicates the highest center-of-mass energy achievable in proton–proton collisions for a given experimental or physical setup.
-
E.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27c98088190a493c9eddf6b206a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.