Triple
T26765476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | charm quark |
E674925
|
entity |
| Predicate | associatedMeson |
P90539
|
FINISHED |
| Object | J/ψ meson |
—
|
NE NERFINISHED |
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: J/ψ meson | Statement: [charm quark, associatedMeson, J/ψ meson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMeson Context triple: [charm quark, associatedMeson, J/ψ meson]
-
A.
associatedMOS
Indicates a relationship where one entity is linked to or paired with a specific Military Occupational Specialty (MOS) code or role.
-
B.
associatedWithParticle
chosen
Indicates that an entity has a contextual or functional connection to a specific particle (such as a subatomic particle or grammatical particle).
-
C.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
D.
associatedMob
Indicates a relationship where one entity is linked or connected to a particular mob (mobile entity), typically as its counterpart, partner, or related unit.
-
E.
associatedMine
Indicates that one entity is linked or connected to a particular mine, typically as its source, location, or relevant mining site.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: April 27, 2026, 3:59 a.m.