Triple
T23269541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XENON |
E588249
|
entity |
| Predicate | targetParticle |
P860
|
FINISHED |
| Object | WIMP |
—
|
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: WIMP | Statement: [XENON, targetParticle, WIMP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetParticle Context triple: [XENON, targetParticle, WIMP]
-
A.
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.
-
B.
beamParticle
Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
-
C.
associatedWithParticle
Indicates that an entity has a contextual or functional connection to a specific particle (such as a subatomic particle or grammatical particle).
-
D.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
E.
targetSide
Indicates the specific side or aspect of a referenced target that is involved in or affected by the relationship or action.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957219188190b30bceffad1542da |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:45 p.m.