Triple
T33588679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faddeev–Popov ghosts |
E860357
|
entity |
| Predicate | appearInGauge |
P5369
|
FINISHED |
| Object | Feynman gauge |
—
|
NE NERFINISHED |
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: Feynman gauge | Statement: [Faddeev–Popov ghosts, appearInGauge, Feynman gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearInGauge Context triple: [Faddeev–Popov ghosts, appearInGauge, Feynman gauge]
-
A.
gaugeServed
Indicates that a gauge or measuring device is currently being supplied or serviced by a particular source or system.
-
B.
gaugeSituation
Indicates assessing or evaluating the current state, conditions, or circumstances of a situation.
-
C.
gaugeValue
Indicates the measured or current reading associated with a particular gauge or measurement instrument.
-
D.
gaugeCompatibleWith
Indicates that one gauge can be properly used with, mounted to, or function correctly in conjunction with another specified component or system.
-
E.
gaugeGroup
chosen
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 1:40 a.m.