Triple
T17105544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 't Hooft coupling |
E415089
|
entity |
| Predicate | limitCondition |
P118901
|
FINISHED |
| Object | N → ∞ with λ fixed |
—
|
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: N → ∞ with λ fixed | Statement: ['t Hooft coupling, limitCondition, N → ∞ with λ fixed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitCondition Context triple: ['t Hooft coupling, limitCondition, N → ∞ with λ fixed]
-
A.
limitExpression
chosen
Indicates that one expression represents the limiting value approached by another expression as some variable or parameter tends toward a specified value or condition.
-
B.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
C.
limitsDefinitionTo
Indicates that one entity constrains or narrows the scope of how another entity is defined or interpreted.
-
D.
limitBehavior
Indicates how an entity behaves or changes as it approaches a specified limit or boundary condition.
-
E.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
- 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.