Triple
T1390293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higgs field |
E29938
|
entity |
| Predicate | hasPotentialForm |
P169
|
FINISHED |
| Object | Mexican hat potential |
—
|
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: Mexican hat potential | Statement: [Higgs field, hasPotentialForm, Mexican hat potential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPotentialForm Context triple: [Higgs field, hasPotentialForm, Mexican hat potential]
-
A.
hasForm
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
hasFullForm
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
-
C.
containsForm
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
D.
hasResourcePotential
Indicates that an entity possesses the capacity or suitability to provide, generate, or support a particular resource in the future.
-
E.
hasNonStandardForm
Indicates that an entity possesses a form, variant, or representation that deviates from the standard, canonical, or commonly accepted form.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35e023c8190b45688796d90534b |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.