Triple
T17105516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 't Hooft anomaly |
E415088
|
entity |
| Predicate | persistsUnder |
P36117
|
FINISHED |
| Object | renormalization group flow |
—
|
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: renormalization group flow | Statement: ['t Hooft anomaly, persistsUnder, renormalization group flow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: persistsUnder Context triple: ['t Hooft anomaly, persistsUnder, renormalization group flow]
-
A.
persistsAfter
chosen
Indicates that one state, condition, or effect continues to exist after a specified event, time point, or other state has occurred or ended.
-
B.
existedUnder
Indicates that one entity existed within the authority, jurisdiction, or domain of another entity during a certain period.
-
C.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
persistence
Indicates a continued or repeated existence, occurrence, or effort of something over time despite potential changes or obstacles.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2683fc81908af2df9012addecb |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.