Triple
T24822874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gauge theory |
E621105
|
entity |
| Predicate | gaugeFixingMethod |
P39342
|
FINISHED |
| Object | axial gauge |
—
|
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: axial gauge | Statement: [gauge theory, gaugeFixingMethod, axial gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaugeFixingMethod Context triple: [gauge theory, gaugeFixingMethod, axial gauge]
-
A.
gaugeInvarianceRequires
Indicates that maintaining gauge invariance necessitates or imposes a specific condition, structure, or constraint on another quantity or element in the theory.
-
B.
gaugeCoupling
Indicates the strength of interaction between fields or particles as defined by a specific gauge symmetry in a physical theory.
-
C.
gaugeTheoryFeature
Indicates a property, structure, or characteristic that specifically pertains to a gauge theory within a physical or mathematical framework.
-
D.
gaugeType
chosen
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
E.
gaugeCompatibleWith
Indicates that one gauge can be properly used with, mounted to, or function correctly in conjunction with another specified component or system.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:05 a.m.