Triple
T9770394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | neutrino hypothesis |
E237108
|
entity |
| Predicate | associatedWithParticle |
P90539
|
FINISHED |
| Object | lepton |
—
|
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: lepton | Statement: [neutrino hypothesis, associatedWithParticle, lepton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithParticle Context triple: [neutrino hypothesis, associatedWithParticle, lepton]
-
A.
associatedWithPub
Indicates that an entity has a connection or relationship with a particular publication (e.g., as source, reference, or related work).
-
B.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
associatedWithFront
Indicates a relationship where one entity is linked or connected specifically to the front part, side, or face of another entity.
-
D.
associatedWithMaterial
Indicates a relationship where something is linked or connected to a particular material, typically as its substance, component, or relevant physical medium.
-
E.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
- F. None of above. chosen
Provenance (4 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f1dea08190b89bcc192b068c66 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:26 p.m.