Triple
T9689360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobayashi–Maskawa theory |
E234497
|
entity |
| Predicate | involvesParticle |
P1256
|
FINISHED |
| Object | up 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: up quark | Statement: [Kobayashi–Maskawa theory, involvesParticle, up quark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesParticle Context triple: [Kobayashi–Maskawa theory, involvesParticle, up quark]
-
A.
involvesParticleTransfer
Indicates that the relationship or action includes the movement or exchange of discrete particles from one entity to another.
-
B.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
C.
usedParticle
Indicates that one entity employs or applies a particular particle (e.g., subatomic, linguistic, or material) in some process, context, or construction involving another entity.
-
D.
involvesPlate
Indicates that an event, action, or situation includes or makes use of a plate as a relevant participant or object.
-
E.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d02b20881909d7c0d5d6aaafcb0 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.