Triple
T26765479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | charm quark |
E674925
|
entity |
| Predicate | associatedBaryon |
P90539
|
FINISHED |
| Object | Λ_c baryon |
—
|
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: Λ_c baryon | Statement: [charm quark, associatedBaryon, Λ_c baryon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBaryon Context triple: [charm quark, associatedBaryon, Λ_c baryon]
-
A.
associatedWithParticle
chosen
Indicates that an entity has a contextual or functional connection to a specific particle (such as a subatomic particle or grammatical particle).
-
B.
associatedStable
Indicates that one entity is linked or connected to a particular stable in a way that denotes an ongoing or defined association.
-
C.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
D.
associatedBody
Indicates a relationship where one entity is linked or connected to another entity as its related or corresponding body.
-
E.
associatedBase
Indicates a relationship where one entity is linked or connected to a corresponding base entity that it depends on or is derived from.
- 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_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: April 27, 2026, 3:59 a.m.