Triple
T33588658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faddeev–Popov ghosts |
E860357
|
entity |
| Predicate | doNotAppearAs |
P159958
|
FINISHED |
| Object | asymptotic physical states |
—
|
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: asymptotic physical states | Statement: [Faddeev–Popov ghosts, doNotAppearAs, asymptotic physical states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doNotAppearAs Context triple: [Faddeev–Popov ghosts, doNotAppearAs, asymptotic physical states]
-
A.
doesNotHide
Indicates that an entity remains visible or transparent about something rather than concealing or obscuring it.
-
B.
doNotApplyTo
Indicates that something is excluded from affecting, covering, or being relevant to a specified target or case.
-
C.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
D.
notTypicallyShownTo
chosen
Indicates that one entity is generally not displayed or presented to another entity under normal circumstances.
-
E.
disappearsWith
Indicates that when one entity ceases to exist, is removed, or becomes unavailable, the other entity simultaneously or consequently also ceases to exist, is removed, or becomes unavailable.
- 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_69f6f77626d08190821cdc5a96e621fb |
completed | May 3, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.