Triple
T1722355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | quantum electrodynamics |
E37418
|
entity |
| Predicate | hasGaugeGroup |
P5369
|
FINISHED |
| Object | U(1) |
—
|
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: U(1) | Statement: [quantum electrodynamics, hasGaugeGroup, U(1)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGaugeGroup Context triple: [quantum electrodynamics, hasGaugeGroup, U(1)]
-
A.
gaugeGroup
chosen
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
-
B.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
C.
hasTaskGroup
Indicates that an entity is associated with, or belongs to, a specific task group that organizes or groups related tasks.
-
D.
hasCategoryGroup
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
-
E.
hasCoveringGroup
Indicates that one group serves as a covering group (typically a covering or universal covering in the group-theoretic sense) for another group.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.