Triple

T33588668
Position Surface form Disambiguated ID Type / Status
Subject Faddeev–Popov ghosts E860357 entity
Predicate enterAs P180833 FINISHED
Object additional fields in the gauge-fixed Lagrangian 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: additional fields in the gauge-fixed Lagrangian | Statement: [Faddeev–Popov ghosts, enterAs, additional fields in the gauge-fixed Lagrangian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: enterAs
Context triple: [Faddeev–Popov ghosts, enterAs, additional fields in the gauge-fixed Lagrangian]
  • A. entersBy
    Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
  • B. enteredInto
    Indicates that one entity has initiated or become formally involved in a particular state, agreement, relationship, or situation with another entity.
  • C. entryMode
    Indicates the manner or method by which something is entered, recorded, or input into a system or context.
  • D. enteredVia
    Indicates that one entity came into or accessed another entity through a specified medium, route, or mechanism.
  • E. entersFrom
    Indicates that one entity moves into or arrives at a place, state, or context by coming from another specified source or location.
  • F. None of above. chosen

Provenance (4 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_69f7516d5b4081908588a6feb541f355 completed May 3, 2026, 1:45 p.m.
PD Predicate disambiguation batch_69f74d40ebb081909daf60623e38f41d completed May 3, 2026, 1:27 p.m.
PDg Predicate description generation batch_69f7516c538481908c6e55cf76add098 completed May 3, 2026, 1:45 p.m.
Created at: May 1, 2026, 1:40 a.m.