Triple
T29992413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALPHA |
E761915
|
entity |
| Predicate | studiesPropertyOfAntihydrogen |
P90254
|
FINISHED |
| Object | hyperfine structure |
—
|
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: hyperfine structure | Statement: [ALPHA, studiesPropertyOfAntihydrogen, hyperfine structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesPropertyOfAntihydrogen Context triple: [ALPHA, studiesPropertyOfAntihydrogen, hyperfine structure]
-
A.
antiprotonsProducedIn
Indicates that antiprotons are generated, created, or produced within or by a specified process, system, or location.
-
B.
studiedProperty
chosen
Indicates that an entity has examined, researched, or analyzed a particular property or attribute of another entity.
-
C.
antiparticleType
Indicates that one particle is the corresponding antiparticle type of another particle.
-
D.
hasAntiquark
Indicates that one particle is associated with, or contains, a corresponding antiquark as part of its composition or structure.
-
E.
isOwnAntiparticle
Indicates that an entity is identical to its own antiparticle, meaning it serves simultaneously as both particle and antiparticle in that 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791b73a081908c15d046673bbc37 |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:39 p.m.