Triple
T7668397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | proton–antiproton collider at CERN |
E173682
|
entity |
| Predicate | discoveryYearOfWAndZ |
P3631
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [proton–antiproton collider at CERN, discoveryYearOfWAndZ, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryYearOfWAndZ Context triple: [proton–antiproton collider at CERN, discoveryYearOfWAndZ, 1983]
-
A.
discoveryYear
chosen
Indicates the calendar year in which something was first discovered or identified.
-
B.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
C.
wereFirstRealizedExperimentallyInYear
Indicates the year in which something was first successfully demonstrated or confirmed through experimental observation or testing.
-
D.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
E.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.