Triple
T613897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi National Accelerator Laboratory |
E12159
|
entity |
| Predicate | contributedToDiscoveryOf |
P477
|
FINISHED |
| Object | top quark |
—
|
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: top quark | Statement: [Fermi National Accelerator Laboratory, contributedToDiscoveryOf, top quark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributedToDiscoveryOf Context triple: [Fermi National Accelerator Laboratory, contributedToDiscoveryOf, top quark]
-
A.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
B.
discoveredBy
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
C.
coDiscovererOf
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
D.
notableContribution
chosen
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
-
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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e0a0f588190b953fdb585263307 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.