Triple
T18912548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall D |
E462642
|
entity |
| Predicate | focusParticleType |
P3639
|
FINISHED |
| Object | mesons |
—
|
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: mesons | Statement: [Hall D, focusParticleType, mesons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusParticleType Context triple: [Hall D, focusParticleType, mesons]
-
A.
hasParticleType
chosen
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
-
B.
dominantParticleType
Indicates that one particle type is the primary or most prevalent component within a given system, context, or interaction.
-
C.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
D.
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.
-
E.
associatedWithParticle
Indicates that an entity has a contextual or functional connection to a specific particle (such as a subatomic particle or grammatical particle).
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c624516c81909e6bf04707d3c71c |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.